@@ -71,10 +71,31 @@ level: 4
7171title : " *[Optional]* Repeat the preceding steps for all other |onprem| hosts in your High Availability deployment."
7272ref : rinse-repeat
7373content : |
74- .. include:: /includes/fact-upgrade-logs-paused.rst
7574
76- If your upgrade is successful, repeat steps 1 to 4 on the next host in your
77- high availability |onprem| deployment.
75+ |onprem| remains in **Upgrade Mode** until every host is upgraded. For
76+ :doc:`high availability configurations </tutorial/configure-application-high-availability>`,
77+ this means:
78+
79+ - Your hosts might not be fully operational until the upgrade is completed
80+ cluster-wide. If your first host upgrade takes longer than expected, continue
81+ upgrading the other hosts.
82+
83+ - Do not stop or cancel processes that seem stuck as this might disrupt the upgrade.
84+
85+ - The logs that |onprem| generates during startup might temporarily pause
86+ at ``Starting pre-flight checks`` while |onprem| upgrades all its servers
87+ to the same version.
88+
89+ - For multi-version upgrades, do not skip major versions.
90+ You must upgrade each node in the cluster to the last minor version of each major release one at a time.
91+ For example, to upgrade from 6.0.26 to 8.0.3, do the following steps on *each node*:
92+
93+ 1. Stop the service on a node (running 6.0.26).
94+ 2. Upgrade to the most recent minor version of 7.0.x.
95+ 3. Start the upgraded host before you move to the next node.
96+ 4. Repeat for all other nodes.
97+ 5. Repeat this process to upgrade each node from 7.0.x to 8.0.3.
98+
7899 ---
79100stepnum : 6
80101level : 4
0 commit comments