Briefly, this error occurs when Elasticsearch cannot identify the cluster due to a missing or mismatched UUID (Universally Unique Identifier). This could be due to a misconfiguration or data corruption. To resolve this issue, you can try the following: 1) Check the cluster settings and ensure the UUID matches across all nodes. 2) If the UUID is missing, you may need to restart the cluster to generate a new one. 3) If data corruption is suspected, consider restoring from a backup. Always ensure to maintain regular backups to prevent data loss.
we recommend you run the Elasticsearch Error Check-Up to resolve this issue and many others.
This guide will explain how to resolve this log and expand on how clusters function in Elasticsearch.
Background
When an Elasticsearch cluster spins up for the first time, Elasticsearch generates a unique identifier for it, known as the cluster UUID.
What does this message mean?
This log message is an INFO message, indicating the unique identification string of the cluster when the cluster starts up.
Every node keeps track of the cluster UUID it is part of and will not join another cluster with a different UUID.
You may also check this by going to `<your-es-host>:9200` in your browser and looking for `cluster_uuid` in the response.
{
"name": "Opster",
"cluster_name": "es_8",
"cluster_uuid": "niwmztQkSpO9ODZGmHuQ",
"version": {
"number": "8.0.0",
"build_flavor": "default",
"build_type": "tar",
"build_hash": "4e6e4eab2297e949ec994e688dad46290d018022",
"build_date": "2022-01-06T23:43:02.825887787Z",
"build_snapshot": false,
"lucene_version": "8.10.1",
"minimum_wire_compatibility_version": "6.8.0",
"minimum_index_compatibility_version": "6.0.0-beta1"
},
"tagline": "You Know, for Search"
}How to reproduce this log
Run the following command to start Elasticsearch from the command line:
./bin/elasticsearch
The following log line will appear in the logs once Elasticsearch has been started.
[2022-02-12T13:12:07,696][INFO ][o.e.c.c.Coordinator ] [ubuntu] cluster UUID [0fnOxVu8SeCi74UoU9bTOg]
Overview
An Elasticsearch cluster consists of a number of servers (nodes) working together as one. Clustering is a technology which enables Elasticsearch to scale up to hundreds of nodes that together are able to store many terabytes of data and respond coherently to large numbers of requests at the same time.
Search or indexing requests will usually be load-balanced across the Elasticsearch data nodes, and the node that receives the request will relay requests to other nodes as necessary and coordinate the response back to the user.
Notes and good things to know
The key elements to clustering are:
Cluster State – Refers to information about which indices are in the cluster, their data mappings and other information that must be shared between all the nodes to ensure that all operations across the cluster are coherent.
Master Node – Each cluster must elect a single master node responsible for coordinating the cluster and ensuring that each node contains an up-to-date copy of the cluster state.
Cluster Formation – Elasticsearch requires a set of configurations to determine how the cluster is formed, which nodes can join the cluster, and how the nodes collectively elect a master node responsible for controlling the cluster state. These configurations are usually held in the elasticsearch.yml config file, environment variables on the node, or within the cluster state.
Node Roles – In small clusters it is common for all nodes to fill all roles; all nodes can store data, become master nodes or process ingestion pipelines. However as the cluster grows, it is common to allocate specific roles to specific nodes in order to simplify configuration and to make operation more efficient. In particular, it is common to define a limited number of dedicated master nodes.
Replication – Data may be replicated across a number of data nodes. This means that if one node goes down, data is not lost. It also means that a search request can be dealt with by more than one node.
Common problems
Many Elasticsearch problems are caused by operations which place an excessive burden on the cluster because they require an excessive amount of information to be held and transmitted between the nodes as part of the cluster state. For example:
- Shards too small
- Too many fields (field explosion)
Problems may also be caused by inadequate configurations causing situations where the Elasticsearch cluster is unable to safely elect a Master node. This situation is discussed further in:
Backups
Because Elasticsearch is a clustered technology, it is not sufficient to have backups of each node’s data directory. This is because the backups will have been made at different times and so there may not be complete coherency between them. As such, the only way to backup an Elasticsearch cluster is through the use of snapshots, which contain the full picture of an index at any one time.
Cluster resilience
When designing an Elasticsearch cluster, it is important to think about cluster resilience. In particular – what happens when a single node goes down? And for larger clusters where several nodes may share common services such as a network or power supply – what happens if that network or power supply goes down? This is where it is useful to ensure that the master eligible nodes are spread across availability zones, and to use shard allocation awareness to ensure that shards are spread across different racks or availability zones in your data center.
Log Context
Log “cluster UUID [{}]” classname is Coordinator.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :
coordinationState.set(new CoordinationState(getLocalNode(); persistedState; electionStrategy));
peerFinder.setCurrentTerm(getCurrentTerm());
configuredHostsResolver.start();
final ClusterState lastAcceptedState = coordinationState.get().getLastAcceptedState();
if (lastAcceptedState.metadata().clusterUUIDCommitted()) {
logger.info("cluster UUID [{}]"; lastAcceptedState.metadata().clusterUUID());
}
final VotingConfiguration votingConfiguration = lastAcceptedState.getLastCommittedConfiguration();
if (singleNodeDiscovery
&& votingConfiguration.isEmpty() == false
&& votingConfiguration.hasQuorum(Collections.singleton(getLocalNode().getId())) == false) {
