This node previously joined a cluster with UUID – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.12-7.15

Briefly, this error occurs when an Elasticsearch node tries to join a cluster with a different UUID than the one it was previously connected to. This could be due to a misconfiguration or a change in the cluster. To resolve this issue, you can either delete the data directory of the node to allow it to join the new cluster, or ensure that the node is connecting to the correct cluster by checking the cluster name and network settings. Always remember to backup your data before making any changes.

This guide will help you check for common problems that cause the log ” This node previously joined a cluster with UUID [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: cluster, node.

Log Context

Log “This node previously joined a cluster with UUID [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 ThreadPool.Names.GENERIC; ValidateJoinRequest::new;
 (request; channel; task) -> {
 final ClusterState localState = currentStateSupplier.get();
 if (localState.metadata().clusterUUIDCommitted() &&
 localState.metadata().clusterUUID().equals(request.getState().metadata().clusterUUID()) == false) {
 throw new CoordinationStateRejectedException("This node previously joined a cluster with UUID [" +
 localState.metadata().clusterUUID() + "] and is now trying to join a different cluster with UUID [" +
 request.getState().metadata().clusterUUID() + "]. " +
 getClusterUuidMismatchExplanation(dataPaths; maxLocalStorageNodes));
 joinValidators.forEach(action -> action.accept(transportService.getLocalNode(); request.getState()));


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?