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

new nodes are not showing up in cluster but i can see them on https://discovery-stage.hub.docker.com/v1/clusters/<mytoken> #1129

Closed
shashiranjan84 opened this Issue Aug 7, 2015 · 6 comments

Comments

Projects
None yet
4 participants
@shashiranjan84

shashiranjan84 commented Aug 7, 2015

I created a swarm cluster some time back. To scale out I planned add two more nodes to swarm.

I used following command to add new node

sudo docker -H tcp://0.0.0.0:2375 run -d swarm join --addr=:2375 token://

I see new nodes on discovery hub with previous created nodes but when i query master node(docker info), it does not show the new nodes.

@chanwit

This comment has been minimized.

Show comment
Hide comment
@chanwit

chanwit Aug 11, 2015

Contributor

@shashiranjan84 maybe it's got some delay before showing newly added nodes?
Decreasing the heartbeat rate to be a small value would help (I think heartbeat's default value is 25s).

Contributor

chanwit commented Aug 11, 2015

@shashiranjan84 maybe it's got some delay before showing newly added nodes?
Decreasing the heartbeat rate to be a small value would help (I think heartbeat's default value is 25s).

@abronan

This comment has been minimized.

Show comment
Hide comment
@abronan

abronan Aug 11, 2015

Contributor

Hi @shashiranjan84, this would help if you can show the debug output that is shown on swarm manage and swarm join (using --debug)? Also what is the version of swarm you are using? Thanks!

Contributor

abronan commented Aug 11, 2015

Hi @shashiranjan84, this would help if you can show the debug output that is shown on swarm manage and swarm join (using --debug)? Also what is the version of swarm you are using? Thanks!

@shashiranjan84

This comment has been minimized.

Show comment
Hide comment
@shashiranjan84

shashiranjan84 Aug 11, 2015

@abronan I am running it in production, so I cant stop the swarm and run the swarm in debug mode.
screenshot 2015-08-11 10 54 48

@chanwit how do we update the heartbeat?

shashiranjan84 commented Aug 11, 2015

@abronan I am running it in production, so I cant stop the swarm and run the swarm in debug mode.
screenshot 2015-08-11 10 54 48

@chanwit how do we update the heartbeat?

@chanwit

This comment has been minimized.

Show comment
Hide comment
@chanwit

chanwit Aug 11, 2015

Contributor

@shashiranjan84 you need to stop the manager and start it again with --heartbeat=1s , for example

Contributor

chanwit commented Aug 11, 2015

@shashiranjan84 you need to stop the manager and start it again with --heartbeat=1s , for example

@aluzzardi

This comment has been minimized.

Show comment
Hide comment
@aluzzardi

aluzzardi Oct 29, 2015

Contributor

Hey @shashiranjan84, sorry this fell through the cracks.

This likely means swarm cannot reach the nodes.

If you can't restart it with the debug flag, you could simply start another swarm with the same token AS LONG as you use it in read-only mode (e.g. don't run containers on it).

My guess is --addr in join was used wrong.

You could try something like this:

In the manage machine, run:

  • swarm list token://<token> and look if you see the address of your new machines
  • Then run docker -H <that same address> info and see if you can reach the engine from that machine
Contributor

aluzzardi commented Oct 29, 2015

Hey @shashiranjan84, sorry this fell through the cracks.

This likely means swarm cannot reach the nodes.

If you can't restart it with the debug flag, you could simply start another swarm with the same token AS LONG as you use it in read-only mode (e.g. don't run containers on it).

My guess is --addr in join was used wrong.

You could try something like this:

In the manage machine, run:

  • swarm list token://<token> and look if you see the address of your new machines
  • Then run docker -H <that same address> info and see if you can reach the engine from that machine
@abronan

This comment has been minimized.

Show comment
Hide comment
@abronan

abronan Dec 17, 2015

Contributor

@shashiranjan84 You most likely solved the issue by now, sorry for the inconvenience. We're working on adding the connection status on docker info to help troubleshoot issues for Node management (in #1486).

Feel free to comment below or reach out on IRC (#docker-swarm) if you still have issues with Swarm. Thanks!

Contributor

abronan commented Dec 17, 2015

@shashiranjan84 You most likely solved the issue by now, sorry for the inconvenience. We're working on adding the connection status on docker info to help troubleshoot issues for Node management (in #1486).

Feel free to comment below or reach out on IRC (#docker-swarm) if you still have issues with Swarm. Thanks!

@abronan abronan closed this Dec 17, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment