No index found to request freeze freeze unfreeze – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch cannot find an index to freeze or unfreeze. This could be due to the index not existing, or the index is already in the desired state (frozen or unfrozen). To resolve this issue, you can verify the existence of the index and its current state. If the index does not exist, create it. If it’s already in the desired state, no action is needed. If it’s in the opposite state, use the appropriate freeze or unfreeze API command.

This guide will help you check for common problems that cause the log ” no index found to ” + (request.freeze() ? “freeze” : “unfreeze ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, index.

Log Context

Log “no index found to ” + (request.freeze() ? “freeze” : “unfreeze” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 || (request.freeze() == false && FrozenEngine.INDEX_FROZEN.get(settings))) {
 if (indices.isEmpty() && request.indicesOptions().allowNoIndices() == false) {
 throw new ResourceNotFoundException("no index found to " + (request.freeze() ? "freeze" : "unfreeze"));
 return indices.toArray(Index.EMPTY_ARRAY);
 }  @Override