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.