docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #863 from docker/large-numbers-802 

Fixed wording for "large version mismatches."
This commit is contained in:
Justin I. Nevill 2018-11-07 11:15:13 -05:00 committed by GitHub
parent f70b3589ad ec8c9888d3
commit 0619ea4d21
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ee/upgrade.md
View File

@ -19,8 +19,8 @@ architecture in Swarm to increase the performance and scale of the built-in load
Docker Engine - Enterprise upgrades in Swarm clusters should follow these guidelines in order to avoid IP address
space exhaustion and associated application downtime.
* New workloads should not be actively scheduled in the cluster during upgrades.
* Large version mismatches between managers and workers can cause unintended consequences when new workloads are scheduled.
* New workloads should not be actively scheduled in the cluster during upgrades.
* Differences in the major (X.y.z.) or minor (x.Y.z) version numbers between the managers and workers can cause unintended consequences when new workloads are scheduled.
* Manager nodes should all be upgraded first before upgrading worker nodes. Upgrading manager nodes sequentially is recommended if live workloads are running in the cluster during the upgrade.
* Once manager nodes are upgraded worker nodes should be upgraded next and then the Swarm cluster upgrade is complete.
* If running UCP, the UCP upgrade should follow once all of the Swarm engines have been upgraded.