Configuring A Failover Domain - Red Hat ENTERPRISE LINUX 4 - ADMINISTRATION Manual

Chapter 3. Configuring Red Hat Cluster With Conga
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 administer 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. The
member at the top of the list is the most preferred, followed by the second member in the list, and so
on.
Note
Changing a failover domain configuration has no effect on currently running services.
Note
Failover domains are not required for operation.
By default, failover domains are unrestricted and unordered.
In a cluster with several members, using a restricted failover domain can minimize the work to set up
the cluster to run a cluster service (such as httpd), which requires you to set up the configuration
identically on all members that run the cluster service). Instead of setting up the entire cluster to
34