No index found to ” + (request.freeze() ? “freeze” : “unfreeze – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

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: index and plugin.

Log Context

Log “no index found to ” + (request.freeze() ? “freeze” : “unfreeze”classname  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);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content