TransportClient node failures


We are on ES 2.4 with 5 Nodes. We are creating 1 replica for all indices. We are using transport client to connect to cluster for search and Index operations. When one of the nodes go down, we are getting various errors and I am wondering how clients are expected to deal with these issue. Errors we are seeing are

  1. java.util.concurrent.ExecutionException: ClusterBlockException[blocked by: [SERVICE_UNAVAILABLE/2/no master];
    We have 3 eligible master nodes and when master nodes and within seconds another node becomes master but we still get the above error
  2. Scroll Not available
  3. [SERVICE_UNAVAILABLE/1/state not recovered / initialized]

Any help on how client code should be updated to handle these scenarios is greatly appreciated

(system) #2

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