Briefly, this error occurs when there’s an attempt to upgrade the lifecycle policy of an Elasticsearch index but the process fails. This could be due to a variety of reasons such as incorrect policy configurations, insufficient permissions, or network issues. To resolve this, you can check and correct the lifecycle policy configurations, ensure the user has the necessary permissions, or troubleshoot any network connectivity issues. Additionally, ensure that the Elasticsearch cluster is running the correct version that supports the lifecycle policy upgrade.
This guide will help you check for common problems that cause the log ” upgrading lifecycle policy [{}] for [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, template.
If you want to learn more about Elasticsearch templates, check out this guide.
Overview
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 “upgrading lifecycle policy [{}] for [{}]” classname is IndexTemplateRegistry.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
final LifecyclePolicy currentPolicy = metadata != null ? metadata.getPolicies().get(policy.getName()) : null;
if (Objects.isNull(currentPolicy)) {
logger.debug("adding lifecycle policy [{}] for [{}]; because it doesn't exist"; policy.getName(); getOrigin());
putPolicy(policy; creationCheck);
} else if (isUpgradeRequired(currentPolicy; policy)) {
logger.info("upgrading lifecycle policy [{}] for [{}]"; policy.getName(); getOrigin());
putPolicy(policy; creationCheck);
} else {
logger.trace("not adding lifecycle policy [{}] for [{}]; because it already exists"; policy.getName(); getOrigin());
creationCheck.set(false);
}
