Cannot restore index renamedIndex because an open index – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.5

Briefly, this error occurs when you try to restore an index in Elasticsearch that has the same name as an existing open index. Elasticsearch doesn’t allow this to prevent data loss. To resolve this issue, you can either close the existing index before restoring, rename the index you’re trying to restore, or delete the existing index if it’s no longer needed. Always ensure to backup your data before performing these operations to prevent accidental data loss.

This guide will help you check for common problems that cause the log ” cannot restore index [” + renamedIndex + “] because an open index ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, restore.

Log Context

Log “cannot restore index [” + renamedIndex + “] because an open index ” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private void validateExistingIndex(IndexMetaData currentIndexMetaData; IndexMetaData snapshotIndexMetaData;
 String renamedIndex; boolean partial) {
 // Index exist - checking that it's closed
 if (currentIndexMetaData.getState() != IndexMetaData.State.CLOSE) {
 // TODO: Enable restore for open indices
 throw new SnapshotRestoreException(snapshot; "cannot restore index [" + renamedIndex + "] because an open index " +
 "with same name already exists in the cluster. Either close or delete the existing index or restore the " +
 "index under a different name by providing a rename pattern and replacement name");
 // Index exist - checking if it's partial restore
 if (partial) {


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?