Restore process is already running in this cluster – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

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 an attempt is made to restore a snapshot while another restore process is already running in the Elasticsearch cluster. Elasticsearch does not support concurrent restore operations. To resolve this issue, you can either wait for the current restore process to complete before initiating a new one, or you can cancel the ongoing restore process if it’s not critical, and then start the new restore operation. Always ensure to monitor your cluster’s activity before initiating a restore operation to avoid such conflicts.

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 ” Restore process is already running in this cluster ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: restore, cluster.

Log Context

Log “Restore process is already running in this cluster” class name is RestoreService.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 RestoreInProgress restoreInProgress = currentState.custom(RestoreInProgress.TYPE; RestoreInProgress.EMPTY);
 if (currentState.getNodes().getMinNodeVersion().before(Version.V_7_0_0)) {
 // Check if another restore process is already running - cannot run two restore processes at the
 // same time in versions prior to 7.0
 if (restoreInProgress.isEmpty() == false) {
 throw new ConcurrentSnapshotExecutionException(snapshot; "Restore process is already running in this cluster");
 }
 }  // Check if the snapshot to restore is currently being deleted
 ensureSnapshotNotDeleted(currentState);

 

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?