status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Be more explicit about rolling upgrade process

This commit is contained in:
Paul Banks 2018-10-11 11:44:20 +01:00
parent 5952804334
commit f951dcfb9d
No known key found for this signature in database
GPG Key ID: C25A851A849B8221
1 changed files with 11 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
website/source/docs/upgrading.html.md
View File

@ -31,7 +31,9 @@ Consul is A, and version B is released.
2. On each server, install version B of Consul.
3. Shut down version A, restart with version B.
3. One server at a time, shut down version A, restart with version B. Wait until
the server is healthy and has rejoined the cluster before moving on to the
next server.
4. Once all the servers are upgraded, begin a rollout of clients following
the same process.
@ -52,12 +54,15 @@ version B comes out.
1. On each node, install version B of Consul.
2. Shut down version A, and start version B with the `-protocol=PREVIOUS`
flag, where "PREVIOUS" is the protocol version of version A (which can
be discovered by running `consul -v` or `consul members`).
2. One server at a time, shut down version A, and start version B with the
`-protocol=PREVIOUS` flag, where "PREVIOUS" is the protocol version of
version A (which can be discovered by running `consul -v` or `consul
members`). Wait until the server is healthy and has rejoined the cluster
before moving on to the next server.
3. Once all nodes are running version B, go through every node and restart
the version B agent _without_ the `-protocol` flag.
3. Once all nodes are running version B, go through every node and restart the
version B agent _without_ the `-protocol` flag, again wait for each server to
rejoin the cluster before continuing.
4. Done! You're now running the latest Consul agent speaking the latest protocol.
You can verify this is the case by running `consul members` to