No action configured for caching strategy cachingStrategy – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch cannot find a configured action for the specified caching strategy. This could be due to a misconfiguration or a typo in the caching strategy name. To resolve this issue, you can check the Elasticsearch configuration files and ensure that the caching strategy is correctly defined. Alternatively, you can also verify that the caching strategy is supported by your version of Elasticsearch. If it’s not supported, you may need to upgrade your Elasticsearch version or use a different caching strategy.

This guide will help you check for common problems that cause the log ” No action configured for caching strategy[” + cachingStrategy + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, analysis.

Log Context

Log “No action configured for caching strategy[” + cachingStrategy + “]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 case LUCENE:
 return new PreBuiltCacheStrategyLucene<>();
 return new PreBuiltCacheStrategyElasticsearch<>();
 throw new ElasticsearchException("No action configured for caching strategy[" + cachingStrategy + "]");
 }  /**
 * This is a pretty simple cache; it only contains one version


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?