# Recover from a Leaf Node Failure

> **❗ Important**: To prevent potential issues, the other availability group must be healthy before performing this operation.

Use the following steps to reintroduce a leaf node to a cluster where [`redundancyLevel` is set to 2](https://docs.singlestore.com/db/v9.1/deploy/kubernetes/create-the-object-definition-files/sdb-cluster-yaml.md) with redundant leaf nodes.

1. Scale down the Operator.
   ```shell
   kubectl scale deployment [operator deployment name] --replicas=0
   ```

2. Scale down the STS with the pod you need to replace. For a leaf node in either of the availability groups, scale down the STS to `0` and then scale it back up to the number of pods in the group.
   ```shell
   kubectl scale statefulsets [StatefulSet Name] --replicas=0
   ```

3. Delete the `PersistentVolumeClaim` (PVC) of the problematic pod.
   ```shell
   kubectl delete pvc pv-storage-node-ccd487dc-3b15-4c3b-88a2-a984dc0245ca-leaf-ag1-0
   ```

4. Delete the pod.
   ```shell
   kubectl delete pod node-ccd487dc-3b15-4c3b-88a2-a984dc0245ca-leaf-ag1-0
   ```

5. Scale the STS and Operator back up.
   ```shell
   kubectl scale statefulsets [StatefulSet Name] --replicas=[num of pods in this StatefulSet]
   ```

***

Modified at: August 27, 2025

Source: [/db/v9.1/reference/singlestore-operator-reference/recover-from-a-leaf-node-failure/](https://docs.singlestore.com/db/v9.1/reference/singlestore-operator-reference/recover-from-a-leaf-node-failure/)

(An index of the documentation is available at /llms.txt)