Installation guide

10. Click Update main fence properties and wait for the change to take effect.
3.6.3. Deleting a Member from a Cluster
To delete a member from an existing cluster that is currently in operation, follow the steps in this section.
The starting point of the procedure is at the Choose a cluster to adm inister page (displayed
on the cluster tab).
1. Click the link of the node to be deleted. Clicking the link of the node to be deleted causes a page
to be displayed for that link showing how that node is configured.
Note
To allow services running on a node to fail over when the node is deleted, skip the next
step.
2. Disable or relocate each service that is running on the node to be deleted:
Note
Repeat this step for each service that needs to be disabled or started on another node.
a. Under Services on this Node, click the link for a service. Clicking that link cause a
configuration page for that service to be displayed.
b. On that page, at the Choose a task drop-down box, choose to either disable the service
are start it on another node and click Go.
c. Upon confirmation that the service has been disabled or started on another node, click the
cluster tab. Clicking the cluster tab causes the Choose a cluster to adm inister
page to be displayed.
d. At the Choose a cluster to administer page, click the link of the node to be
deleted. Clicking the link of the node to be deleted causes a page to be displayed for that
link showing how that node is configured.
3. On that page, at the Choose a task drop-down box, choose Delete this node and click Go.
When the node is deleted, a page is displayed that lists the nodes in the cluster. Check the list to
make sure that the node has been deleted.
3.7. Configuring a Failover Domain
A failover domain is a named subset of cluster nodes that are eligible to run a cluster service in the
event of a node failure. A failover domain can have the following characteristics:
Unrestricted — Allows you to specify that a subset of members are preferred, but that a cluster
service assigned to this domain can run on any available member.
Restricted — Allows you to restrict the members that can run a particular cluster service. If none of
the members in a restricted failover domain are available, the cluster service cannot be started
(either manually or by the cluster software).
Unordered — When a cluster service is assigned to an unordered failover domain, the member on
which the cluster service runs is chosen from the available failover domain members with no priority
ordering.
Ordered — Allows you to specify a preference order among the members of a failover domain. T he
Chapter 3. Configuring Red Hat Cluster With Conga
39