We are running Elasticsearch 0.90.2 on Debian 7.0/OpenJDK7u3 (2 nodes
From time to time, Elasticsearch stop responding and the issue looks
related to the Garbage Collector.
Here are the information we have collected when problems occur :
-The search threadpool hits the concurrent active items limit and the queue
limit (default values, ie 36 threads and 1000 slots in the queue).
-We have high rate of slow queries (>8 seconds)
-The garbage collector logs long passes (around 6 seconds)
-Clients get Rejected exceptions
All of this happens for several minutes (> 10) from time to time
Then everything get back to normal.
Logs are attached.
The values we have :
System total memory : 6GB
We are almost sure this issue comes from long GC run.
We are planning to change the GC for G1 (after upgrading to Java 7u25,
because this GC requires Java 7u4), but I've seen in this group one thread
saying it crashes:/
What can we do to prevent this behavior and run ES smoothly ?
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@example.com.
For more options, visit https://groups.google.com/groups/opt_out.