No index found to ” + (request.freeze() ? “freeze” : “unfreeze – Elasticsearch Error How To Solve Related Issues

No index found to ” + (request.freeze() ? “freeze” : “unfreeze – Elasticsearch Error How To Solve Related Issues

Updated: July-20

Elasticsearch Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up  which can resolve issues causing many errors 


This guide will help you check for common problems that cause the log “no index found to ” + (request.freeze() ? “freeze” : “unfreeze” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: index, plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to discover the cause of many errors and provides suitable actionable recommendations (free tool that requires no installation). 

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);


Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :





About Opster

Opster detects, prevents, optimizes and automates everything needed to run mission-critical Elasticsearch

Find Configuration Errors

Analyze Now