Skip to content

Commit 181fdb2

Browse files
sumanthravipatiSumanth Ravipati
andauthored
CLD-574: Documentation updates to remove host
Co-authored-by: Sumanth Ravipati <[email protected]>
1 parent 67a89eb commit 181fdb2

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

README.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -311,7 +311,21 @@ In order to track the host shutdown progress, run the following command:
311311
kubectl logs pod/terminated-host-pod-name
312312
```
313313

314-
If you are permanently removing the host from the MarkLogic cluster, once the pod is terminated, follow standard MarkLogic administrative procedures using the administrative UI or APIs to remove the MarkLogic host from the cluster. Also, because Kubernetes keeps the Persistent Volume Claims and Persistent Volumes around until they are explicitly deleted, you must manually delete them using the Kubernetes APIs before attempting to scale the hosts in the StatefulSet back up again.
314+
If you are permanently removing the host from the MarkLogic cluster, once the pod is terminated, follow the section "Recovery - Step 3: Remove dead host configuration" in [MarkLogic KB article](https://help.marklogic.com/Knowledgebase/Article/View/607/15/replacing-a-failed-marklogic-node-in-a-cluster-a-step-by-step-walkthrough). Also, because Kubernetes keeps the Persistent Volume Claims and Persistent Volumes around until they are explicitly deleted, you must manually delete them using the Kubernetes APIs before attempting to scale the hosts in the StatefulSet back up again.
315+
316+
In order to delete the Persistent Volumes and Persistent Volume Claims of the terminated host first run the below command to get the Persistent Volume Claims:
317+
```
318+
kubectl get pvc datadir-<terminated-host-pod-name>
319+
```
320+
To delete the Persistent Volume run the below command:
321+
```
322+
kubectl delete pv <volume name from get pvc command>
323+
```
324+
To delete the Persistent Volume Claims run the below command:
325+
```
326+
kubectl delete pvc datadir-<terminated-host-pod-name>
327+
```
328+
315329
### Enabling SSL over XDQP
316330

317331
To enable SSL over XDQP, set the `enableXdqpSsl` to true either in the values.yaml file or using the `--set` flag. All communications to and from hosts in the cluster will be secured. When this setting is on, default SSL certificates will be used for XDQP encryption.

0 commit comments

Comments
 (0)