I am using ES 2.2 with Java client 2.2.
I have 3 node ES cluster. 2 Master + Data. 1 dedicated Data node.
I have set the discovery.zen.minimum_master_nodes: 2 to avoid split brain.
In my transport-client I have given all 3 nodes IP to connect.
In a good case scenarios I am getting an expected behavior.
If I create a network disconnect between 2 masters, I see that my cluster size is reduced to 2 from 3.
One node is isolated constantly trying to connect to the cluster.
But my transportclient fails giving me MasterNotDiscoveredException.
Note that my write was on before I created a disconnect.
I was assuming that Transportclient should only use nodes which are connected in the cluster.
Here, it should rebalance itself to use only 2.
But it seems that it is blindly doing round robin to all the nodes and the one which is isolated is throwing this
Isnt that incorrect? What am I missing?