Cannot migrate because that index does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.16-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 you’re trying to migrate or perform an operation on an Elasticsearch index that doesn’t exist. This could be due to a typo in the index name or the index was deleted. To resolve this issue, you can verify the index name and ensure it exists before performing operations. If the index was deleted, you may need to recreate it or restore it from a backup. Also, ensure that your Elasticsearch cluster is in a healthy state and that there are no network connectivity issues.

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 ” cannot migrate because that index does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index.

Log Context

Log “cannot migrate because that index does not exist” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  if (stateIndexName != null && clusterState.metadata().hasIndex(stateIndexName) == false) {
 markAsFailed(new IndexNotFoundException(stateIndexName; "cannot migrate because that index does not exist"));
 } else {
 stateIndexName = null;
 stateFeatureName = null;


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?