Policy not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.5-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch cannot find the specified index lifecycle management (ILM) policy. This could be due to the policy not being created, being deleted, or a typo in the policy name. To resolve this issue, you can check if the policy exists using the Get Lifecycle Policy API. If it doesn’t exist, you need to create it using the Put Lifecycle Policy API. If the policy name is incorrect, correct it in your request. Also, ensure that the ILM feature is enabled in your Elasticsearch setup.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” policy [{}] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “policy [{}] not found” class name is EnrichStore.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  updateClusterState(clusterService; handler; current -> {
 final Map policies = getPolicies(current);
 if (policies.containsKey(name) == false) {
 throw new ResourceNotFoundException("policy [{}] not found"; name);
 }  policies.remove(name);
 return policies;


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?