New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NullPointerException when running through bound ports #13676
Comments
I tried to start to Elasticsearch nodes on the same port and the second one gave me:
and then an exception. And then stopped. Which seems to be just about right. |
I just tried it with 1.7.2 running on the same port and binding to the same interface as master. Master reported the same failure. I then tried 1.7.2. and 2.0.0. Then 2.0.0 holding the port with 1.7.2 trying to bind to it. All reported a relatively sane error message. |
Given what I've seen so far I'm going to close this. @drewr feel free to reopen if I've reproduced this the wrong way around. |
I'm trying to upgrade from 1.7.2 to 2.0.0 and I run into this issue. I upgraded ES to 2.0.0 on one of the client nodes, installed the new version of the cloud-aws plugin as described here: https://www.elastic.co/guide/en/elasticsearch/plugins/current/cloud-aws.html (naturally, I removed the previous version first). When I'm restarting the upgraded node, I'm getting:
Am I missing something obvious here? |
This is a duplicate of #14400 |
If there is already an ES running on a port and we try to bind to it, you can get weird errors. In case they're NPEs, I'm assuming because it's 2.x trying to talk to 1.4.4. We should handle this more gracefully.
The text was updated successfully, but these errors were encountered: