Hello, in our Elasticsearch 2.3.4 implementation we've been experiencing the dreaded "No nodes available, transport -1" issue. After looking at varius topics regarding the issue, the issues I've checked is NOT the problem is:
- Cluster name. We're using default "elasticsearch" name and that is what I see in the java code and when I go directly to ip:elasticport when I check my browser.
Also, our setup is that it pulls data from a remote server every 2 minutes, then it sends it to elasticsearch. We're only getting the error (which we read from catalina.out) about once every second log, however sometimes it can be three times in one log. So it's not something that happens all the time.
This lead me to looking at the question of checking whether or not the port may be closing down every once in a while. I am by no means any expert on networking, but google gave me a few ways of checking whether it's "open", and it's at least listening.
We're running the logger in one docker and elasticsearch in another, both on the same server if that helps anyone trying to figure this out. I should also mention that the current logger was working "as it should" prior to a week ago, however we're in the process of upgrading to ES 5.3 and happened to crash the old one in that process and had to grab the old war file from git and start the docker again.
Thanks for your time.