# \[ES 1.1.1\] Java Client - random NoNodeAvailable

**URL:** <https://discuss.elastic.co/t/es-1-1-1-java-client-random-nonodeavailable/20136>\
**Category:** Elasticsearch\
**Created:** [October 8, 2014, 10:02am UTC](https://discuss.elastic.co/t/es-1-1-1-java-client-random-nonodeavailable/20136 "2014-10-08T10:02:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sheliak\_lyr](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@sheliak\_lyr](https://discuss.elastic.co/u/sheliak_lyr)\
**Post date:** [October 8, 2014, 10:02am UTC](https://discuss.elastic.co/t/es-1-1-1-java-client-random-nonodeavailable/20136/1 "2014-10-08T10:02:10Z")

</div>

Hello,

My application is written in Java and uses Java Elasticsearch Client  
(1.1.1).

On my build server, I set up a single ES server instance and have multiple  
plans with integration tests.  
Each plan:

1. Removes indices/aliases from ES (only those that are required by this  
plan) - this takes a few seconds
2. Creates indices/aliases/mappings etc. - this step takes about 45  
seconds
3. Performs integration tests

Sometimes, everything works. But usually one of the plans fails because of  
NoNodeAvailable exception at step 2/3. I've enabled debug logs and found  
TimeoutException:

org.elasticsearch.transport.ReceiveTimeoutTransportException: [][inet[/10.132.4.197:9311]][cluster/nodes/info] request\_id [8] timed out after [5001ms]

```
at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:356)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:724)

```

Increasing timout to 10s did not help. After setting it to 60s the builds are stable (for now..).

5 seconds is a lot of time for simple ping. Do you have any idea what may cause such problem?

Additional info:

- problem occurs only when plans are run in parallel,
- ES server has 2g memory (Xmx, Xms) and mlock set to true - there  
should be no problems with memory
- logs on server contain no errors
- unicast is used to connect to server
- number of indices: 45 (per single plan)
- shards per index: 2, 0 replicas

Thanks!

Sheliak

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/398fc3a1-6a3f-486f-93a0-87b930b66196%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/398fc3a1-6a3f-486f-93a0-87b930b66196%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:57am UTC](https://discuss.elastic.co/t/es-1-1-1-java-client-random-nonodeavailable/20136/2 "2017-07-06T00:57:42Z")

</div>


