Cloud: NoNodeAvailableException after some time of connectivity

Elastic Stack Elasticsearch
1

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.

2

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

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

3

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

4

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