# Master Node election not working

**URL:** <https://discuss.elastic.co/t/master-node-election-not-working/245097>\
**Category:** Elasticsearch\
**Tags:** elastic-agent\
**Created:** [August 15, 2020, 1:38pm UTC](https://discuss.elastic.co/t/master-node-election-not-working/245097 "2020-08-15T13:38:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jijo.john](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jijo.john](https://discuss.elastic.co/u/jijo.john)\
**Post date:** [August 15, 2020, 1:38pm UTC](https://discuss.elastic.co/t/master-node-election-not-working/245097/1 "2020-08-15T13:38:04Z")

</div>

Hi Team,

We are running a POC on elastic search. We have three nodes

Node 1:  
node.master: true  
node.data: true  
node.ingest: true  
node.ml: false  
cluster.initial\_master\_nodes: ["ibs-dc-siem-1", "ibs-dc-siem-backup"]

Node 2:  
node.data: true  
node.master: true  
node.voting\_only: false  
node.ingest: true  
node.ml: false  
node.attr.box\_type: hot  
cluster.initial\_master\_nodes: ["ibs-dc-siem-1", "ibs-dc-siem-backup"]

Node 3: (Coordinating Node)  
node.data: false  
node.master: false  
node.ingest: false  
node.ml: false

If Node 1 Goes down , Kibana on all three goes down and Node 2 will not become master

If Node 2 goes down , Kibana will be available from Node 1, Node 2 and Node 3 all works fine.

Below is the error we get from kibana

`{"statusCode":500,"error":"Internal Server Error","message":"all shards failed: [node\_not\_connected\_exception] [ibs-dc-siem-1][10.181.10.176:9300] Node not connected"}

# Output When all three nodes are UP

GET /\_cat/nodes  
10.181.10.176 5 99 19 1.61 1.15 0.76 dim \* ibs-dc-siem-1  
10.181.10.12 60 98 7 0.52 0.28 0.28 dim - ibs-dc-siem-backup  
10.181.10.5 20 89 0 0.11 0.09 0.11 - - ibs-dc-siem-cn

GET \_cat/master  
6Kc\_4PJcTyKUPeAzvKRUCQ 10.181.10.176 10.181.10.176 ibs-dc-siem-1

Is there any more config to be done . Please help to resolve this

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 15, 2020, 2:12pm UTC](https://discuss.elastic.co/t/master-node-election-not-working/245097/2 "2020-08-15T14:12:42Z")

</div>

I would recommend you read [this](https://www.elastic.co/guide/en/elasticsearch/reference/7.8/high-availability-cluster-small-clusters.html). Just because you can make different nodes have different roles does not mean this is a good idea in a small cluster. I would recommend that you set up all nodes with default configuration and start from there. Your current configuration does not make much sense to me and I do not understand what you are trying to achieve or learn from it.

---

<div class="post-metadata">

**Author:** ![jijo.john](https://avatars.discourse-cdn.com/v4/letter/j/b3f665/32.png) [@jijo.john](https://discuss.elastic.co/u/jijo.john)\
**Post date:** [August 15, 2020, 7:19pm UTC](https://discuss.elastic.co/t/master-node-election-not-working/245097/3 "2020-08-15T19:19:15Z")

</div>

Hi Christian,

Thank you very much for pointing this document. I was able configure the nodes as per the doc and its worked perfectly. I am new to elasticsearch and we are doing a POC with small cluster with few clients pointed to it.

Thanks,  
Jijo John

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 12, 2020, 7:19pm UTC](https://discuss.elastic.co/t/master-node-election-not-working/245097/4 "2020-09-12T19:19:17Z")

</div>

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