5.5.4. Adding a GULM Client-only Member
The procedure for adding a member to a running GULM cluster depends on the type of GULM node: either a node that functions only as a GULM client (a cluster member capable of running applications, but not eligible to function as a GULM lock server) or a node that functions as a GULM lock server. This procedure describes how to add a member that functions only as a GULM client. To add a member that functions as a GULM lock server, refer to Section 5.5.6, “Adding or Deleting a GULM Lock Server Member”.
To add a member that functions only as a GULM client to an existing cluster that is currently in operation, follow these steps:
- At one of the running members, start
system-config-cluster(refer to Section 5.2, “Starting the Cluster Configuration Tool”). At the Cluster Configuration Tool tab, add the node and configure fencing for it as in Section 5.5.1, “Adding a Member to a New Cluster”.
- Click Send to Cluster 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.
- Start cluster services on the new node by running the following commands in this order:
service ccsd start
service lock_gulmd start
service clvmd start, if CLVM has been used to create clustered volumes
service gfs start, if you are using Red Hat GFS
service rgmanager start, if the cluster is running high-availability services (
system-config-cluster, in 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.
Make sure to configure other parameters that may be affected by changes in this section. Refer to Section 5.1, “Configuration Tasks”.