Master not discovered or elected yet, an election requires 2 nodes with ids

Elastic Stack Elasticsearch
1

I have three node clusters, one of which is a master node. The master node has been lost and there are only two slave nodes at present. However, after I rejoin the new master node, it cannot work properly
[node33] master not discovered or elected yet, an election requires 2 nodes with ids [HPrlKfNoScmqH4LnOTekyw, D95Ry_8QTSapAILszIjEbw], have discovered [{node33}{D95Ry_8QTSapAILszIjEbw}{JTsZQFP0SRK57eiqUMfszQ}{172.16.60.33}{172.16.60.33:9300}{dilm}{ml.machine_memory=68419936256, xpack.installed=true, ml.max_open_jobs=20}, {node36}{xetNFXHoRKqhxauGYl4Bqg}{ZfuCtTiNTDChzI4yZXoqxw}{172.16.60.36}{172.16.60.36:9300}{dilm}{ml.machine_memory=68419932160, ml.max_open_jobs=20, xpack.installed=true}, {node34}{HPrlKfNoScmqH4LnOTekyw}{gCSn1Sg6QmeXI68Zr6by2w}{172.16.60.34}{172.16.60.34:9300}{dilm}{ml.machine_memory=67501502464, ml.max_open_jobs=20, xpack.installed=true}] which is a quorum; discovery will continue using [172.16.60.34:9300, 172.16.60.36:9300] from hosts providers and [{node33}{D95Ry_8QTSapAILszIjEbw}{JTsZQFP0SRK57eiqUMfszQ}{172.16.60.33}{172.16.60.33:9300}{dilm}{ml.machine_memory=68419936256, xpack.installed=true, ml.max_open_jobs=20}] from last-known cluster state; node term 0, last-accepted version 0 in term 0

2

Having a cluster with only one master eligible node means you have no resilience. As the master node hold the state, losing this means you may have also lost the data. I would recommend setting up a new cluster and restoring from a snapshot. If this is not possible you might find some guidance here.

3
  • Thank you. That helped me a lot
4

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