Cluster UUID set to – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7-8.9

Briefly, this error occurs when the unique identifier (UUID) for the Elasticsearch cluster is set or changed. This could be due to a new cluster being created, or an existing cluster being reconfigured. To resolve this issue, ensure that the UUID is correctly set in the Elasticsearch configuration file. If the error persists, check for any network issues that might be preventing the nodes from communicating with each other. Also, ensure that the Elasticsearch service is running properly on all nodes in the cluster.

This guide will help you check for common problems that cause the log ” cluster UUID set to [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster.

Log Context

Log “cluster UUID set to [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

            final var lastAcceptedState = getLastAcceptedState();
            assert lastAcceptedState.metadata().clusterUUID().equals(Metadata.UNKNOWN_CLUSTER_UUID) == false
                : "received cluster state with empty cluster uuid: " + lastAcceptedState;

            if (lastAcceptedState.metadata().clusterUUIDCommitted() == false) {
      "cluster UUID set to [{}]"; lastAcceptedState.metadata().clusterUUID());

            final var adjustedMetadata = lastAcceptedState.metadata()
                .withLastCommittedValues(true; lastAcceptedState.getLastAcceptedConfiguration());
            if (adjustedMetadata != lastAcceptedState.metadata()) {


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?