Skip to content

Commit 0643d22

Browse files
authored
Merge pull request #86503 from lahinson/ocpbugs-28595-etcd-graceful
[OCPBUGS-28595]: Applying changes to etcd graceful shutdown docs to main
2 parents 06f99a4 + 3a7402d commit 0643d22

File tree

1 file changed

+10
-15
lines changed

1 file changed

+10
-15
lines changed

modules/graceful-shutdown.adoc

Lines changed: 10 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -65,13 +65,20 @@ node/ci-ln-mgdnf4b-72292-n547t-worker-c-vcmtn cordoned
6565
$ for node in $(oc get nodes -l node-role.kubernetes.io/worker -o jsonpath='{.items[*].metadata.name}'); do echo ${node} ; oc adm drain ${node} --delete-emptydir-data --ignore-daemonsets=true --timeout=15s --force ; done
6666
----
6767

68-
. Shut down all of the nodes in the cluster. You can do this from your cloud provider’s web console, or by running the following loop:
68+
. Shut down all of the nodes in the cluster. You can do this from the web console for your cloud provider web console, or by running the following loop. Shutting down the nodes by using one of these methods allows pods to terminate gracefully, which reduces the chance for data corruption.
69+
+
70+
[NOTE]
71+
====
72+
Ensure that the control plane node with the API VIP assigned is the last node processed in the loop. Otherwise, the shutdown command fails.
73+
====
6974
+
7075
[source,terminal]
7176
----
72-
$ for node in $(oc get nodes -o jsonpath='{.items[*].metadata.name}'); do oc debug node/${node} -- chroot /host shutdown -h 1; done
77+
$ for node in $(oc get nodes -o jsonpath='{.items[*].metadata.name}'); do oc debug node/${node} -- chroot /host shutdown -h 1; done <1>
7378
----
7479
+
80+
<1> `-h 1` indicates how long, in minutes, this process lasts before the control plane nodes are shut down. For large-scale clusters with 10 nodes or more, set to `-h 10` or longer to make sure all the compute nodes have time to shut down first.
81+
+
7582
.Example output
7683
[source,terminal]
7784
----
@@ -84,18 +91,6 @@ To use host binaries, run `chroot /host`
8491
Shutdown scheduled for Mon 2021-09-13 09:36:29 UTC, use 'shutdown -c' to cancel.
8592
----
8693
+
87-
Shutting down the nodes using one of these methods allows pods to terminate gracefully, which reduces the chance for data corruption.
88-
+
89-
[NOTE]
90-
====
91-
Adjust the shut down time to be longer for large-scale clusters:
92-
93-
[source,terminal]
94-
----
95-
$ for node in $(oc get nodes -o jsonpath='{.items[*].metadata.name}'); do oc debug node/${node} -- chroot /host shutdown -h 10; done
96-
----
97-
====
98-
+
9994
[NOTE]
10095
====
10196
It is not necessary to drain control plane nodes of the standard pods that ship with {product-title} prior to shutdown.
@@ -107,4 +102,4 @@ Cluster administrators are responsible for ensuring a clean restart of their own
107102
[IMPORTANT]
108103
====
109104
If you deployed your cluster on a cloud-provider platform, do not shut down, suspend, or delete the associated cloud resources. If you delete the cloud resources of a suspended virtual machine, {product-title} might not restore successfully.
110-
====
105+
====

0 commit comments

Comments
 (0)