-
Notifications
You must be signed in to change notification settings - Fork 862
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
Filter Discovered peers for ipv6 support #6498
Filter Discovered peers for ipv6 support #6498
Conversation
|
b9d08c7
to
ebf915b
Compare
d9d5aab
to
260d6b4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left two comments, but LGTM
.orElseGet(sourceEndpoint::getHost); | ||
.orElseGet( | ||
() -> { | ||
LOG.trace( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LOG.atTrace would be nice ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since this is already in a lambda, the extra log lambda isn't necessary :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh wait, yeah. you are right! I originally had this logging every time, but it was noisy and moved it to trace
@@ -173,4 +196,20 @@ private static boolean isPortAvailableForUdp(final int port) { | |||
public static boolean isPortAvailable(final int port) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've had a look at the isPortAvailableFor[Tcp|Udp] and I thought that we might want to close the ServerSocket if we successfully binded to it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently SO_REUSEADDR makes it moot, but I don't see why we wouldn't unbind. It isn't in the scope of this PR, but I can put up a subsequent one.
…ltering, add ipv6 check/fallback Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
260d6b4
to
7dc8bc7
Compare
Signed-off-by: garyschulte <[email protected]>
1757144
to
59da07a
Compare
Signed-off-by: garyschulte <[email protected]>
Signed-off-by: garyschulte <[email protected]>
* use existing NetworkUtility for PeerDiscoveryAgent pingpacket data filtering, add ipv6 check/fallback * log at debug when we override pingpacket from * use java native address parsing rather than lookup by host Signed-off-by: garyschulte <[email protected]> Signed-off-by: Gabriel-Trintinalia <[email protected]>
PR description
updates PeerDiscoveryAgent to
Fixed Issue(s)
fixes #6475