Cluster is not running and master is not discovered

Elastic Stack Elasticsearch
1

I'm running an Elasticsearch 7.3.2 cluster, which was recently bootstrapped with 3 nodes:

The cluster was running well until yesterday when I needed to make a full cluster shutdown.

Now the cluster is not running and /_cat/health calls on every node returns status 503:

{
"error": {
"root_cause": [
{
"type": "master_not_discovered_exception",
"reason": null
}
],
"type": "master_not_discovered_exception",
"reason": null
},
"status": 503
}

This is the complete Elasticsearch configuration on all three nodes:

cluster.name: mycluster
node.name: elasticX.domain.com
path.data: /var/lib/elasticsearch
path.logs: /var/log/elasticsearch
bootstrap.memory_lock: true
network.host: 0.0.0.0
http.port: 9200
discovery.seed_hosts: ["elastic1.domain.com", "elastic2.domain.com", "elastic3.domain.com"]
cluster.initial_master_nodes: ["elastic1.domain.com", "elastic2.domain.com", "elastic3.domain.com"]

Could you help me to understand where I'm wrong, and how I can recover my cluster, please?

2

Is the storage used persistent?

3

Yes, it is.
Nodes are installed on local storage and not in containers like Dockers.

4

Did any firewall rules change?

5

No, nodes can correctly see each others and there are no blocking firewall rules.

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.