I have 2 node cluster and 1 java process running the redexing jobs for
every minute using TransportClient.
I take down 1 node, and the client can fail over and continue to
work without problem
suddenly the client have timeout to get local cluster state and
exception is thrown:
and from all the subsequent index requests submitted by the
TransportClient, exception "No node available" is thrown and it cannot
recover by itself even the node is still there and up.
when I bring the downed node (the one taken down in step 1), the
TransportClient can detect and resume to conncet to the cluster
Does that mean the TransportClient will not resume when the last
member of the cluster "timeout"?