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

The default network interface selection chooses wrong interface in some cases #11795

Closed
kwart opened this issue Nov 15, 2017 · 0 comments
Closed

The default network interface selection chooses wrong interface in some cases #11795

kwart opened this issue Nov 15, 2017 · 0 comments

Comments

@kwart
Copy link
Contributor

@kwart kwart commented Nov 15, 2017

This issue is based on existing PR: #11504

Hazelcast binds to a wrong network interface in some cases. The problem is with network interfaces which are not UP (e.g. Docker uses such interface for in-host communication).

The problem is in DefaultAddressPicker class which doesn't check network interface status. The DefaultAddressPicker is responsible for selecting a network interface for Hazelcast. It picks the first available non-loopback IP address.

Suggested fix
Change the DefaultAddressPicker implementation so it filters out network interfaces which are:

  • DOWN
  • or loopback
  • or virtual
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.

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