# Master Node Goes down + Transport Client always connecting to Elected Master

**URL:** <https://discuss.elastic.co/t/master-node-goes-down-transport-client-always-connecting-to-elected-master/190297>\
**Category:** Elasticsearch\
**Created:** [July 12, 2019, 7:35pm UTC](https://discuss.elastic.co/t/master-node-goes-down-transport-client-always-connecting-to-elected-master/190297 "2019-07-12T19:35:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [July 12, 2019, 7:35pm UTC](https://discuss.elastic.co/t/master-node-goes-down-transport-client-always-connecting-to-elected-master/190297/1 "2019-07-12T19:35:19Z")

</div>

ES Version 6.x, Transport Client 6.x

We see the behavior of elected master using high CPU and JVM always, and goes off when it reaches a higher number ~75% removing and restarting node. I'm suspicious whether it is due to transport client sending all the requests to the same master node though the sniffing is enabled.  
network.host is 0.0.0.0 in all nodes. It is the IPs of 3 master nodes that are given for initial connectivity.

The JVM/CPU on all other nodes is well below 20%/70%. Elected master keeps reaching high CPU/JVM and goes off

Any guidance on this would be helpful.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 13, 2019, 6:23am UTC](https://discuss.elastic.co/t/master-node-goes-down-transport-client-always-connecting-to-elected-master/190297/2 "2019-07-13T06:23:52Z")

</div>

You should switch to the Rest Client.  
The TransportClient is removed in 8.0.

---

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [July 15, 2019, 6:11pm UTC](https://discuss.elastic.co/t/master-node-goes-down-transport-client-always-connecting-to-elected-master/190297/3 "2019-07-15T18:11:02Z")

</div>

Hi David,

THanks for response.

Yes. We would be migrating to Rest Client, and is part of our road-map. But, it is not something that would happen soon and our current clusters are in 6.x with Transport Client. We are getting this issue now. Trying to see if we are missing anything as we see the JVM and CPU keeps going up on elected master=\> LOoks like all connections from Transport Client is sent only to the same.

---

<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:** [August 12, 2019, 6:11pm UTC](https://discuss.elastic.co/t/master-node-goes-down-transport-client-always-connecting-to-elected-master/190297/4 "2019-08-12T18:11:09Z")

</div>

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