Updated: July-20
Elasticsearch Version: 1.7-8.0
Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues causing many errors
This guide will help you check for common problems that cause the log “component template matching ” + request.name() + ” not found” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: admin, request, template, indices.
Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation).
Template in Elasticsearch
What it is
A template in Elasticsearch falls into one of the two following categories and is indexed inside Elasticsearch using its dedicated endpoint:
- Index Templates, which are a way to define a set of rules including index settings, mappings and an index pattern. The template is applied automatically whenever a new index is created with the matching pattern. Templates are also used to dynamically apply custom mapping for the fields which are not predefined inside existing mapping.
- Search Templates, which help in defining templates for search queries using mustache scripting language. These templates act as a placeholder for variables defined inside the search queries.
Examples
Create a dynamic index template
PUT /_template/template_1?pretty
{
"index_patterns": [
"logs*",
"api*"
],
"settings": {
"number_of_shards": 2
},
"mappings": {
"dynamic_templates": [
{
"strings": {
"match_mapping_type": "string",
"mapping": {
"type": "keyword"
}
}
}
],
"properties": {
"host_name": {
"type": "keyword"
},
"created_at": {
"type": "date"
}
}
}
}
Create a search template
POST /_scripts/search_template_1?pretty
{
"script": {
"lang": "mustache",
"source": {
"query": {
"match": {
"description": "{{query_string}}"
}
}
}
}
}
Executing a search query using search template
GET /_search/template?pretty
{
"id": "search_template_1",
"params": {
"query_string": "hello world"
}
}
The search request will be executed by default on all the indices available in the cluster and can be limited to particular indices using an index parameter.
Notes
A dynamic index template is always useful when you do not know the field names in advance and want to control their mapping as per the business use case.
Log Context
Log”component template matching [” + request.name() + “] not found”classname is TransportGetComponentTemplateAction.java
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
}
} else if (allTemplates.containsKey(name)) {
results.put(name; allTemplates.get(name));
} else {
throw new ResourceNotFoundException("component template matching [" + request.name() + "] not found");
}
listener.onResponse(new GetComponentTemplateAction.Response(results));
}
}
Related issues to this log
We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :
1 Maximum call stack size exceeded error -views 1,217,022 ,score 539
2 Error: Can't set headers after they are sent to the client -views 915,581,score 741
About Opster
Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch
