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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/398fc3a1-6a3f-486f-93a0-87b930b66196%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
