Transport client exception

When 1 of my nodes (cluster of 3 nodes) is down, I get org.elasticsearch.transport.ConnectTransportException
when performing an action future using transport client.
I then wait some time for the cluster to be stable and perform the future action again.
Unfortunately, I can see that the future was already performed successfully while I was waiting for the cluster.
Is this some sort of retry behavior of transport client? Should I give up from retrying myself and let the client do that?
Maybe just sample the future response? until when?


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