# Resolving a NoNodeAvailableException caused by large GCs **URL:** \ **Category:** Elasticsearch\ **Created:** [April 29, 2014, 7:56pm UTC](https://discuss.elastic.co/t/resolving-a-nonodeavailableexception-caused-by-large-gcs/17268 "2014-04-29T19:56:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Rico\_Chiu](https://avatars.discourse-cdn.com/v4/letter/r/258eb7/32.png) [@Rico\_Chiu](https://discuss.elastic.co/u/Rico_Chiu)\ **Post date:** [April 29, 2014, 7:56pm UTC](https://discuss.elastic.co/t/resolving-a-nonodeavailableexception-caused-by-large-gcs/17268/1 "2014-04-29T19:56:45Z")
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 end of [http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html](http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html). 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 time out. Is this the correct solution given this problem? Is it necessary to increase both the interval and timeout? Rico -- 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/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![ad1](https://avatars.discourse-cdn.com/v4/letter/a/e5b9ba/32.png) [@ad1](https://discuss.elastic.co/u/ad1)\ **Post date:** [April 29, 2014, 8:03pm UTC](https://discuss.elastic.co/t/resolving-a-nonodeavailableexception-caused-by-large-gcs/17268/2 "2014-04-29T20:03:11Z")
+1 for this question -- 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/55cda6e6-f089-4c2a-8e6f-4486d8b64cd3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/55cda6e6-f089-4c2a-8e6f-4486d8b64cd3%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\ **Post date:** [April 29, 2014, 9:42pm UTC](https://discuss.elastic.co/t/resolving-a-nonodeavailableexception-caused-by-large-gcs/17268/3 "2014-04-29T21:42:52Z")
You should try to reduce stop-the-world GC as much as possible. Increasing the timeout only makes you not being aware of it. You fight the symptom, not the cause. Jörg On Tue, Apr 29, 2014 at 9:56 PM, Rico Chiu [rico.chiu@gmail.com](mailto:rico.chiu@gmail.com) wrote: > 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 end of > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/client/java-api/current/client.html). > 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 > time out. > > Is this the correct solution given this problem? Is it necessary to > increase both the interval and timeout? > > Rico > > -- > 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/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/b24b9736-13f6-437d-897a-065d089ef604%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- 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/CAKdsXoHECriLj6Ey8DjZ6N09t4hGnDyN9so2RSpchrHNUsJZQA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHECriLj6Ey8DjZ6N09t4hGnDyN9so2RSpchrHNUsJZQA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:32am UTC](https://discuss.elastic.co/t/resolving-a-nonodeavailableexception-caused-by-large-gcs/17268/4 "2017-07-06T01:32:40Z")
Closed on July 6, 2017, 1:32am UTC