# Cloud: NoNodeAvailableException after some time of connectivity

**URL:** <https://discuss.elastic.co/t/cloud-nonodeavailableexception-after-some-time-of-connectivity/76400>\
**Category:** Elasticsearch\
**Created:** [February 24, 2017, 12:53pm UTC](https://discuss.elastic.co/t/cloud-nonodeavailableexception-after-some-time-of-connectivity/76400 "2017-02-24T12:53:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![djmcgreal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djmcgreal/32/52956_2.png) [@djmcgreal](https://discuss.elastic.co/u/djmcgreal)\
**Post date:** [February 24, 2017, 12:53pm UTC](https://discuss.elastic.co/t/cloud-nonodeavailableexception-after-some-time-of-connectivity/76400/1 "2017-02-24T12:53:54Z")

</div>

Hi all,

I'm running into e.g. a `NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{f9PviRNJSribEeZ4TkMY3g}{74403af429071821d485db89e9c0a357.eu-west-1.aws.found.io}{176.34.243.129:9343}]]` after some time of operation, even though the connection is ostensibly available. As soon as I recreate the connection, it works. I'm wondering if there is a) some problem of caching ip addresses (and the endpoint for ES Cloud's IP changes) or if there is some other problem in the Java Client.

Best, Dan.

---

<div class="post-metadata">

**Author:** ![ywelsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ywelsch/32/7751_2.png) [@ywelsch](https://discuss.elastic.co/u/ywelsch)\
**Post date:** [February 24, 2017, 1:25pm UTC](https://discuss.elastic.co/t/cloud-nonodeavailableexception-after-some-time-of-connectivity/76400/2 "2017-02-24T13:25:15Z")

</div>

Maybe related to this: [https://discuss.elastic.co/t/nonodeavailableexception-with-java-transport-client/37702](https://discuss.elastic.co/t/nonodeavailableexception-with-java-transport-client/37702) and/or [https://github.com/elastic/elasticsearch/pull/21630](https://github.com/elastic/elasticsearch/pull/21630) ?

Which ES version are you using? What is your transport client configuration?

---

<div class="post-metadata">

**Author:** ![djmcgreal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/djmcgreal/32/52956_2.png) [@djmcgreal](https://discuss.elastic.co/u/djmcgreal)\
**Post date:** [February 24, 2017, 1:55pm UTC](https://discuss.elastic.co/t/cloud-nonodeavailableexception-after-some-time-of-connectivity/76400/3 "2017-02-24T13:55:41Z")

</div>

Thanks, that thread is exactly in line with my suspicions on the cause of this - I just did my search in the wrong forum.

---

<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:** [March 24, 2017, 1:55pm UTC](https://discuss.elastic.co/t/cloud-nonodeavailableexception-after-some-time-of-connectivity/76400/4 "2017-03-24T13:55:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.