4.5.3. Deleting a Member from a Cluster

4.5.3. Deleting a Member from a Cluster

To delete a member from an existing cluster that is currently in operation, follow these steps:

  1. At one of the running nodes (not to be removed), run the Red Hat Cluster Suite management GUI. At the Cluster Status Tool tab, under Services, disable or relocate each service that is running on the node to be deleted.

  2. Stop the cluster software on the node to be deleted by running the following commands at that node in this order:

    1. service rgmanager stop

    2. service gfs stop, if you are using Red Hat GFS

    3. service clvmd stop

    4. service fenced stop (DLM clusters only)

    5. service cman stop (or service lock_gulmd stop for GULM clusters)

    6. service ccsd stop

  3. At the Cluster Configuration Tool (on one of the running members), delete the member as follows:

    1. If necessary, click the triangle icon to expand the Cluster Nodes property.

    2. Select the cluster node to be deleted. At the bottom of the right frame (labeled Properties), click the Delete Node button.

    3. Clicking the Delete Node button causes a warning dialog box to be displayed requesting confirmation of the deletion (Figure 4.6, “Confirm Deleting a Member”).

      Confirm Deleting a Member

      [D]

      Figure 4.6. Confirm Deleting a Member

    4. At that dialog box, click Yes to confirm deletion.

    5. Propagate the updated configuration by clicking the Send to Cluster button. (Propagating the updated configuration automatically saves the configuration.)

  4. Stop the cluster software on the remaining running nodes (including GULM lock-server nodes for GULM clusters) by running the following commands at each node in this order:

    1. service rgmanager stop

    2. service gfs stop, if you are using Red Hat GFS

    3. service clvmd stop

    4. service fenced stop (DLM clusters only)

    5. service cman stop (or service lock_gulmd stop for GULM clusters)

    6. service ccsd stop

  5. Start cluster software on all remaining cluster nodes (including GULM lock-server nodes for GULM clusters) by running the following commands in this order:

    1. service ccsd start

    2. service cman start (or service lock_gulmd start for GULM clusters)

    3. service fenced start (DLM clusters only)

    4. service clvmd start

    5. service gfs start, if you are using Red Hat GFS

    6. service rgmanager start

  6. Start the Red Hat Cluster Suite management GUI. 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: This documentation is provided {and copyrighted} by Red Hat®, Inc. and is released via the Open Publication License. The copyright holder has added the further requirement that Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder. The CentOS project redistributes these original works (in their unmodified form) as a reference for CentOS-4 because CentOS-4 is built from publicly available, open source SRPMS. The documentation is unmodified to be compliant with upstream distribution policy. Neither CentOS-4 nor the CentOS Project are in any way affiliated with or sponsored by Red Hat®, Inc.