Skip to content

Commit 3e0a428

Browse files
author
Barkha Choithani
committed
added readme instructions for deploying separate e/d node
1 parent a883985 commit 3e0a428

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

README.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -272,6 +272,23 @@ kubectl logs pod/terminated-host-pod-name
272272
```
273273

274274
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.
275+
276+
## Deploying separate E/D node MarkLogic Cluster
277+
278+
To deploy a MarkLogic cluster with separate E/D group nodes, configure `bootstrapHostName` and `group.name` in values.yaml or provide values for these configurations using --set flag while installing helm charts.
279+
For example, if you want to create a MarkLogic cluster with dnode/enode groups and two nodes in each group, run the following helm commands:
280+
281+
```
282+
helm install dnode-group ./charts/ --set group.name=dnode --set replicaCount=2
283+
```
284+
Once this deployment is completed, MarkLogic cluster with dnode group and two hosts should be running.
285+
While adding enode group and nodes to the cluster, `bootstrapHostName` is needed to join MarkLogic cluster. Use dnode-group-marklogic-0 hostname from Admin console and set it to `bootstrapHostName` configuration in the following command:
286+
287+
```
288+
helm install enode-group ./charts/ --set group.name=enode --set replicaCount=2 --set bootstrapHostName=dnode-group-marklogic-0
289+
```
290+
After this deployment is completed, enode group will be created on the MarkLogic cluster and two hosts will join the cluster.
291+
275292
# Access the MarkLogic Server
276293

277294
## Service

0 commit comments

Comments
 (0)