I recently hit a NoNodeAvailableException while performing a search query.
I was able to deduce that the reason behind this was due to large GC events
occurring on the elasticsearch process, causing the (one and only) node to
be unresponsive. The GCs were around 10-30s long.
I was able to mitigate this problem by increasing both the client transport
ping timeout and nodes sampler interval setting values, as described at the
I felt it was necessary to also increase the sampler value to equal or
greater than the timeout value, since it doesn't make sense to ping the
availability of a node a second time before the first one has the chance to
Is this the correct solution given this problem? Is it necessary to
increase both the interval and timeout?
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.