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
JDK/JRE 7 update 72 breaks multicast in 1.4.0.Beta1 #8225
Comments
Yay! We're in the process of upgrading to 7u72 right now. Happy times. If it needs an assignee I can look at it on Monday. I need an excuse to go poking around in this code. OTOH if someone has time to work on it please don't let me stop you. Your Monday probably starts before mine anyway. |
@nik9000 Note that I've currently tested it on Windows - there's a slim chance, the bug doesn't occur on *nix machines... |
Ah. Well, I'll at least be able to test that on Monday. I don't think my wife would appreciate me commandeering her machine to reproduce on Windows. So if it doesn't reproduce on unix I'd probably be a bad person to work on it. |
I'm on Windows 8.1 but I can't reproduce:
Am I doing something wrong here @costin ? |
Looks like the issue can be reproduced only on Win 8.1 SP1 with both u71 and u72. Elasticsearch ran fine on Win 7 and Win 8.1 (no SP1). In my opinion, this is not a blocker any more however there is work on the way to provide a fix for it. |
@costin I'm also not able to reproduce this running Win 8.1. What is considered SP1? I can't seem to find any updates being referred to as SP1. The latest update I have installed is KB2995388.
|
In case the multicast binding fails (due to socket errors), abort zen pinging code and throw a better error message Relates elastic#8225
Based on various feedback it seems that I am the only one running into this issue which suggests there's some configuration issue with my system. The win 7, win 8.1 (with and without Update 1/ SP1) that we have tested, do not seem to be affected. @clintongormley Hence why I removed the two labels above (critical and blocker). |
@nik9000 see the comment above - I don't think you're going to be affected and anyway, there's a fix already in the works (see the PR). |
Jenkins seeing similar, if the the same failure on window 2012 r2 server 1> [2014-10-27 17:59:39,689][DEBUG][discovery.zen.ping.multicast] [node_t0] failed to send multicast ping request |
Notice the |
In case the multicast binding fails (due to socket errors), abort zen pinging code and throw a better error message Relates #8225
In case the multicast binding fails (due to socket errors), abort zen pinging code and throw a better error message Relates #8225
Pushed the fix in 1.3, 1.4, 1.x and master. In case of a socket error (for whatever reason) a nicer message is displayed to the user and the zen code is skipped (otherwise it causes its own exceptions which only add to the confusion). |
In case the multicast binding fails (due to socket errors), abort zen pinging code and throw a better error message Relates elastic#8225 (cherry picked from commit f819cff)
In case the multicast binding fails (due to socket errors), abort zen pinging code and throw a better error message Relates elastic#8225
I've just updated to JDK 7 update 72 and 1.4.0.Beta1 doesn't work any more (win 8.1).
1.4.0.Beta1 works fine with 7u67 and 8u25. It looks like only 7u72 is problematic (potentially 7u71).
Tested 1.3.4 on 7u72 and it seems to be
working fine.Verified the java version and the same problem occurs - clearly something has changed in the JDK.
The text was updated successfully, but these errors were encountered: