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

Multiple Datanodes and gateway problem #9

Open
aabergaa opened this issue May 2, 2017 · 0 comments
Open

Multiple Datanodes and gateway problem #9

aabergaa opened this issue May 2, 2017 · 0 comments
Labels

Comments

@aabergaa
Copy link

aabergaa commented May 2, 2017

Not sure if this is the best spot to ask a question, but I'm not on the hub much so thought I'd give it a try.

When I launch my master running the resourcemanager and namenode, followed by another container for a data node things seem alright. I then launch a second data node - with different "hostname", and the first one gets dropped as LOST. It still has its services running, but the resource manager doesn't see it anymore. I can restart services on the first and the second one will disappear. After some investigating, I tagged this to them being setup to run off the gateway when they connect to the RM? for instance, a new one will add on 192.168.56.1:50010 - the gateway address of the docker network. I start the next one, watch the logs, and it also adds and registers as a new node, also at 192.168.56.1:50010. Repeat, Repeat, Repeat whether starting new or restarting "LOST" datanodes.

Am I not starting this properly or is there an undocumented secret to get them to associate to their docker ip address rather than the docker network' gateway address?

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

No branches or pull requests

2 participants