Este contenido no está disponible en el idioma seleccionado.
5.5.2. Adding a Member to a Running DLM Cluster
The procedure for adding a member to a running DLM cluster depends on whether the cluster contains only two nodes or more than two nodes. To add a member to a running DLM cluster, follow the steps in one of the following sections according to the number of nodes in the cluster:
- For clusters with only two nodes —
- For clusters with more than two nodes —
5.5.2.1. Adding a Member to a Running DLM Cluster That Contains Only Two Nodes
To add a member to an existing DLM cluster that is currently in operation, and contains only two nodes, follow these steps:
- Add the node and configure fencing for it as in Section 5.5.1, “Adding a Member to a New Cluster”.
- Click to propagate the updated configuration to other running nodes in the cluster.
- Use the
scpcommand to send the updated/etc/cluster/cluster.conffile from one of the existing cluster nodes to the new node. - At
system-config-cluster, in the Cluster Status Tool tab, disable each service listed under . - Stop the cluster software on the two running nodes by running the following commands at each node in this order:
service rgmanager stop, if the cluster is running high-availability services (rgmanager)service gfs stop, if you are using Red Hat GFSservice clvmd stop, if CLVM has been used to create clustered volumesservice fenced stopservice cman stopservice ccsd stop
- Start cluster software on all cluster nodes (including the added one) by running the following commands in this order:
service ccsd startservice cman startservice fenced startservice clvmd start, if CLVM has been used to create clustered volumesservice gfs start, if you are using Red Hat GFSservice rgmanager start, if the cluster is running high-availability services (rgmanager)
- Start
system-config-cluster(refer to Section 5.2, “Starting the Cluster Configuration Tool”). At the Cluster Configuration Tool tab, verify that the configuration is correct. At the Cluster Status Tool tab verify that the nodes and services are running as expected.
Note
Make sure to configure other parameters that may be affected by changes in this section. Refer to Section 5.1, “Configuration Tasks”.
