You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vCluster automatically recovers from single replica failures, including replica-0, within 10 minutes. Manual intervention is only required if automatic recovery does not complete or if the majority of replicas have failed simultaneously.
162
+
:::
172
163
173
-
<InterpolatedCodeBlock
174
-
code={`kubectl get pods -l [[VAR:VCLUSTER LABEL:app=vcluster]] -n [[VAR:NAMESPACE:vcluster-my-team]]`}
175
-
language="bash"
176
-
/>
177
-
</Step>
164
+
:::note
165
+
This recovery procedure works for both `podManagementPolicy: Parallel` (default) and `podManagementPolicy: OrderedReady` (legacy) configurations.
166
+
:::
178
167
179
-
<Step title="Delete the corrupted PersistentVolumeClaim">
180
-
Delete the corrupted PVC for the first replica:
168
+
<Flow>
169
+
<Step title="Wait for automatic recovery">
170
+
Monitor the vCluster pods and wait for automatic recovery to complete:
Automatic recovery removes the failed member from the etcd cluster, deletes the pod, and adds it back. The pod restarts with a fresh PVC and rejoins the cluster automatically.
228
189
</Step>
229
190
230
-
<Step title="Scale up vCluster to verify recovery">
231
-
Start with one replica to verify the restored data:
191
+
<Step title="Manual recovery if automatic fails">
192
+
If automatic recovery does not complete after 10 minutes, manually trigger recovery by deleting the failed pod and PVC:
0 commit comments