Multiple nodes trying to upgrade in parallel retry – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 5-5

Briefly, this error occurs when multiple nodes in an Elasticsearch cluster attempt to upgrade simultaneously. This can lead to conflicts and inconsistencies in the cluster state. To resolve this issue, you can follow these steps: 1) Ensure that only one node is upgraded at a time. 2) If the error persists, try restarting the nodes one by one. 3) Check the cluster health and ensure all nodes are in sync before proceeding with the upgrade. 4) If the problem continues, consider rolling back the upgrade and consult with an Elasticsearch expert.

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


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?