I get the following message when performing an expensive query using the Java Client:
org.elasticsearch.client.transport: [Nightside] failed to get node info for {#transport#-1}{x.x.x.x}{x.x.x.x:9300}, disconnecting... ! org.elasticsearch.transport.ReceiveTimeoutTransportException: [][x.x.x.x:9300][cluster:monitor/nodes/liveness] request_id [40362] timed out after [5000ms] ! at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:679) ~ ! at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_40] ! at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_40] ! at java.lang.Thread.run(Thread.java:745) [na:1.8.0_40] org.elasticsearch.transport.netty: [Nightside] disconnecting from [{#transport#-1}{x.x.x.x}{x.x.x.x:9300}] due to explicit disconnect call org.elasticsearch.transport.netty: [Nightside] connected to node [{#transport#-1}{x.x.x.x}{x.x.x.x:9300}]
Is it worth increasing the transport.ping_schedule parameter? Is there anything else I can do to avoid this?
ES Version: 2.3.3