From 6ba2d1144f8638f6f2fcc13843c2e49cfc04570a Mon Sep 17 00:00:00 2001 From: Everett Toews Date: Mon, 31 Aug 2015 11:57:33 -0500 Subject: [PATCH] Fix manager-X to match code and docs Signed-off-by: Everett Toews --- docs/multi-manager-setup.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/multi-manager-setup.md b/docs/multi-manager-setup.md index 155f67e0e1..c14b089617 100644 --- a/docs/multi-manager-setup.md +++ b/docs/multi-manager-setup.md @@ -32,7 +32,7 @@ You need either a `Consul`, `etcd`, or `Zookeeper` cluster. This procedure is wr ### Create the primary manager You use the `swarm manage` command with the `--replication` and `--advertise` flags to create a primary manager. - + user@manager-1 $ swarm manage -H :4000 --replication --advertise 192.168.42.200:4000 consul://192.168.42.10:8500/nodes INFO[0000] Listening for HTTP addr=:4000 proto=tcp INFO[0000] Cluster leadership acquired @@ -59,7 +59,7 @@ This command creates a replica manager on `192.168.42.201:4000` which is looking Create an additional, third *manager* instance: - user@manager-2 $ swarm manage -H :4000 --replication --advertise 192.168.42.202:4000 consul://192.168.42.10:8500/nodes + user@manager-3 $ swarm manage -H :4000 --replication --advertise 192.168.42.202:4000 consul://192.168.42.10:8500/nodes INFO[0000] Listening for HTTP addr=:4000 proto=tcp INFO[0000] Cluster leadership lost INFO[0000] New leader elected: 192.168.42.200:4000 @@ -120,7 +120,7 @@ Issue a `Ctrl-C` or `kill` the current primary manager (`manager-1`) to shut it After a short time, the other instances detect the failure and a replica takes the *lead* to become the primary manager. -For example, look at `manager-1`'s logs: +For example, look at `manager-2`'s logs: user@manager-2 $ swarm manage -H :4000 --replication --advertise 192.168.42.201:4000 consul://192.168.42.10:8500/nodes INFO[0000] Listening for HTTP addr=:4000 proto=tcp @@ -162,4 +162,4 @@ To switch the `DOCKER_HOST` to use `manager-2` as the primary, you do the follow You can use the `docker` command on any Docker Swarm primary manager or any replica. -If you like, you can use custom mechanisms to always point `DOCKER_HOST` to the current primary manager. Then, you never lose contact with your Docker Swarm in the event of a failover. \ No newline at end of file +If you like, you can use custom mechanisms to always point `DOCKER_HOST` to the current primary manager. Then, you never lose contact with your Docker Swarm in the event of a failover.