Installation guide

b. On that page, at the Ch o o se a t askdrop-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 clu st er tab. Clicking the clu st er 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 Ch o o se a t askdrop-down box, choose Delet e t h is n o d e 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.
Failback — Allows you to specify whether a service in the failover domain should fail back to the
node that it was originally running on before that node failed. Configuring this characteristic is
useful in circumstances where a node repeatedly fails and is part of an ordered failover domain.
In that circumstance, if a node is the preferred node in a failover domain, it is possible for a
service to fail over and fail back repeatedly between the preferred node and another node,
causing severe impact on performance.
Note
The failback characteristic is applicable only if ordered failover is configured.
Note
Changing a failover domain configuration has no effect on currently running services.
Red Hat Ent erprise Linux 5 Clust er Administ rat ion
4 4