Skip to content
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

Switch to IPv6 is not seamless #11820

Closed
kwart opened this issue Nov 20, 2017 · 1 comment
Closed

Switch to IPv6 is not seamless #11820

kwart opened this issue Nov 20, 2017 · 1 comment

Comments

@kwart
Copy link
Contributor

@kwart kwart commented Nov 20, 2017

When I enable IPv6 for Hazelcast, the started member still sets an IPv4 as a local address by default.

Hazelcast reference manual talks about a seamless support of IPv6, so the current behavior is unexpected.

Reproducer:

System.setProperty("java.net.preferIPv4Stack", "false");
System.setProperty("java.net.preferIPv6Addresses", "true");
System.setProperty("hazelcast.prefer.ipv4.stack", "false");

Hazelcast.newHazelcastInstance();

and its output:

INFO: [LOCAL] [dev] [3.9] Picked [172.17.0.1]:5701, using socket ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true
Nov 20, 2017 1:36:48 PM com.hazelcast.system
INFO: [172.17.0.1]:5701 [dev] [3.9] Hazelcast 3.9 (20171018 - 4e89e6d) starting at [172.17.0.1]:5701
...

Expected behavior
When IPv6 is enabled/preferred, Hazelcast picks an IPv6 address to bind to.

@Donnerbart
Copy link
Contributor

@Donnerbart Donnerbart commented Nov 20, 2017

IPv6 seems to be not tested well, see the coverage of TcpIpConnector: https://hazelcast-l337.sonar.cloudbees.com/resource/index/35831?display_title=true&metric=coverage

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants
You can’t perform that action at this time.