From b5cce0ce8b101e224c49f45e795d2da3507b6187 Mon Sep 17 00:00:00 2001 From: Hao Jiang <45571951+jianghao0718@users.noreply.github.com> Date: Mon, 13 Sep 2021 21:29:42 -0400 Subject: [PATCH] Update how we upgrade cluster (#21484) --- .../configuring-clustering/upgrading-a-cluster.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md b/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md index af6d8b4b1182..ddd5a62aaf1c 100644 --- a/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md +++ b/content/admin/enterprise-management/configuring-clustering/upgrading-a-cluster.md @@ -79,5 +79,7 @@ Run the `ghe-upgrade` command, providing the package file name you downloaded in > gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u > gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > " ``` -5. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots. -6. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`. +5. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots.{% ifversion ghes > 2.22 %} +6. Connect to the administrative shell of the primary MySQL node and run the `ghe-cluster-config-apply` command. +7. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.{% endif %} +8. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`.