# Repeated NoNodeAvailableExceptions Exceptions **URL:** \ **Category:** Elasticsearch\ **Created:** [January 24, 2017, 8:47pm UTC](https://discuss.elastic.co/t/repeated-nonodeavailableexceptions-exceptions/72698 "2017-01-24T20:47:49Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![amugofjava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amugofjava/32/75350_2.png) [@amugofjava](https://discuss.elastic.co/u/amugofjava)\ **Post date:** [January 24, 2017, 8:47pm UTC](https://discuss.elastic.co/t/repeated-nonodeavailableexceptions-exceptions/72698/1 "2017-01-24T20:47:49Z")
Hi all. I'm finding that I am getting repeated NodeDisconnectedException and NoNodeAvailableExceptions exceptions when running relatively few concurrent queries - fewer than 20. I think I am beginning to understand the reason why but some confirmation would be most appreciated. The default queue size is 1000 and the default number of shards per index is 5. A query against each shard uses 1 in the queue. So, for example, querying against 20 indexes with 5 shards each you would only need to run 101 concurrent queries to go over the default queue size and cause these exceptions? Is my understanding correct? Thanks, Ben. ---
**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\ **Post date:** [January 24, 2017, 11:40pm UTC](https://discuss.elastic.co/t/repeated-nonodeavailableexceptions-exceptions/72698/2 "2017-01-24T23:40:39Z")
> [@amugofjava](#): > > The default queue size is 1000 and the default number of shards per index is 5. > A query against each shard uses 1 in the queue. So, for example, querying > against 20 indexes with 5 shards each you would only need to run 101 concurrent > queries to go over the default queue size and cause these exceptions? That queue size is for the action-specific threadpool, it should not affect the `NodeDisconnectedException` and `NoNodeAvailableException` failures that you are seeing, those exceptions are because either a node has been disconnected and detected with fault detection, or a node cannot be contacted. You should check the logs for the full message for the node disconnection exceptions and see whether they failed during communication. ---
**Author:** ![amugofjava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amugofjava/32/75350_2.png) [@amugofjava](https://discuss.elastic.co/u/amugofjava)\ **Post date:** [January 25, 2017, 6:44am UTC](https://discuss.elastic.co/t/repeated-nonodeavailableexceptions-exceptions/72698/3 "2017-01-25T06:44:20Z")
Hi Lee, Thanks for the reply. I am not seeing anything in the Elasticsearch logs on either node. All the errors are logged on the client side which I have pasted below. I have tried a few options on the Transport client such as turning sniff on and increasing the ping and node sampler interval values but this has made no difference. Is there anything I can do to help debug the error? I am using v5.1.2 of both Elasticsearch and the Java client. My setup consists of two virtual machines each with 2 CPUs, 4GB RAM and 2GB allocated to the JVM. Thanks. None of the configured nodes were available: [{escluster-es2}{-iqECyceSn2FBSPbg-nFvw}{F2PCjdZTTUujzj5996um6w}{192.168.0.222}{192.168.0.222:9300}, {escluster-es1}{WELN6zJ8QYy40zew1Axs2w}{Zc4W94tbT7exlRHziAnd-g}{192.168.0.221}{192.168.0.221:9300}]: NoNodeAvailableException[None of the configured nodes were available: [{escluster-es2}{-iqECyceSn2FBSPbg-nFvw}{F2PCjdZTTUujzj5996um6w}{192.168.0.222}{192.168.0.222:9300}, {escluster-es1}{WELN6zJ8QYy40zew1Axs2w}{Zc4W94tbT7exlRHziAnd-g}{192.168.0.221}{192.168.0.221:9300}]]; nested: NodeDisconnectedException[[escluster-es1][192.168.0.221:9300][indices:data/read/search] disconnected]; at org.elasticsearch.client.transport.TransportClientNodesService$RetryListener.onFailure(TransportClientNodesService.java:266) at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:51) at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:955) at org.elasticsearch.transport.TransportService$Adapter.lambda$raiseNodeDisconnected$3(TransportService.java:783) at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:451) 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: NodeDisconnectedException[[escluster-es1][192.168.0.221:9300][indices:data/read/search] disconnected] ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 22, 2017, 6:44am UTC](https://discuss.elastic.co/t/repeated-nonodeavailableexceptions-exceptions/72698/4 "2017-02-22T06:44:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.