We are using ES 1.4.4 in our production setup. For ES DR setup., our main DC indexer will index in parallel threads in main DC ES cluster using Node Client and DR ES cluster using TransportClient.
We are facing NoNodeAvailableException when sending DeleteRequest in BulkRequest to DR ES cluster at random times (50 to 60 exceptions / day).
org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes were available: [[Node1][6JVz783wRmG-IWBiaDP8mw][IP1][inet[/IP1:9300]]{data=false, max_l
ocal_storage_nodes=1, master=true}, [Node0][rqCavDw4TZKuFCsY9a2wqQ][IP2][inet[/IP2:9300]]{data=false, max_local_storage_nodes=1, master=true}, [Node2][Dtx_m78pSvSsCzb0gJcDiw][IP3][inet[/IP3:9300]]{data=false, max_local_storage_nodes=1, master=true}]
at org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:234)
at org.elasticsearch.action.TransportActionNodeProxy$1.handleException(TransportActionNodeProxy.java:78)
at org.elasticsearch.transport.TransportService$Adapter$3.run(TransportService.java:323)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.elasticsearch.transport.NodeDisconnectedException: [Node2][inet[/IP3:9300]][indices:data/write/bulk] disconnected
Does anyone faced similar issue ? Please help us in resolving this issue.
Thanks in advance
Ranjith Venkatesan