Multiple nodes trying to upgrade in parallel. retry – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many 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 ” Multiple nodes trying to upgrade in parallel. retry ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index and upgrade.

Log Context

Log “multiple nodes trying to upgrade [{}] in parallel; retry” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             Files.move(source; target; StandardCopyOption.ATOMIC_MOVE);
            success = true;
        } catch (NoSuchFileException | FileNotFoundException exception) {
            // thrown when the source is non-existent because the folder was renamed
            // by another node (shared FS) after we checked if the target exists
            logger.error((Supplier>) () -> new ParameterizedMessage("multiple nodes trying to upgrade [{}] in parallel; retry " +
                "upgrading with single node"; target); exception);
            throw exception;
        } finally {
            if (success) {
      "{} moved from [{}] to [{}]"; index; source; target);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content