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

Calculate the appropriate Coordinator IP address #21

Open
karya0 opened this issue Nov 15, 2014 · 1 comment
Open

Calculate the appropriate Coordinator IP address #21

karya0 opened this issue Nov 15, 2014 · 1 comment

Comments

@karya0
Copy link
Member

karya0 commented Nov 15, 2014

Currently, the coordinator uses a mix ot hackery and tricks to compute its IP address. This involves a call to gethostname() followed by a call to getaddrinfo(). This is still unreliable and can give us 127.0.0.1 as the IP address, when we actually need the non-loopback IP.

@jiajuncao
Copy link
Contributor

@karya0 127.0.0.1 is given in the scenario where dmtcp_launch has no --host parameter. At this point, SharedData is not initialized. If ENV_VAR_NAME_HOST is not set, hostname is set to DEFAULT_HOST, which is 127.0.0.1. _coordinatorSocket is then created using this address, which is wrong. This is harmless when running a local computation. But for a distributed one, remote processes won't connect to the correct coordinator.

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

No branches or pull requests

2 participants