Skip to content

Commit d3d095f

Browse files
authored
Merge pull request #56519 from xenolinux/restart-shutdown
OCPBUGS#3813: Restarting and shutting down the cluster
2 parents b768e17 + 4a6aae8 commit d3d095f

File tree

2 files changed

+12
-1
lines changed

2 files changed

+12
-1
lines changed

backup_and_restore/graceful-cluster-shutdown.adoc

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,9 @@ This document describes the process to gracefully shut down your cluster. You mi
1616
include::modules/graceful-shutdown.adoc[leveloffset=+1]
1717

1818
[role="_additional-resources"]
19-
.Additional resources
19+
[id="additional-resources_restarting-restoring-cluster"]
20+
== Additional resources
2021

2122
* xref:../backup_and_restore/graceful-cluster-restart.adoc#graceful-restart-cluster[Restarting the cluster gracefully]
23+
24+
* xref:../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[Restore to a previous cluster state]

modules/graceful-shutdown.adoc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,14 @@ You can shut down a cluster until a year from the installation date and expect i
2121
[IMPORTANT]
2222
====
2323
It is important to take an etcd backup before performing this procedure so that your cluster can be restored if you encounter any issues when restarting the cluster.
24+
25+
For example, the following conditions can cause the restarted cluster to malfunction:
26+
27+
* etcd data corruption during shutdown
28+
* Node failure due to hardware
29+
* Network connectivity issues
30+
31+
If your cluster fails to recover, follow the steps to restore to a previous cluster state.
2432
====
2533

2634
.Procedure

0 commit comments

Comments
 (0)