Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 3 49
Failover Policy
The Package Manager selects a node for a package to run on based on the
priority list included in the package configuration file together with the
FAILOVER_POLICY parameter, also coded in the file. Failover policy
governs how the package manager selects which node to run a package
on when a specific node has not been identified and the package needs to
be started. This applies not only to failovers but also to startup for the
package, including the initial startup. The two failover policies are
CONFIGURED_NODE (the default) and MIN_PACKAGE_NODE. The parameter
is coded in the package ASCII configuration file:
# Enter the failover policy for this package. This policy will be used
# to select an adoptive node whenever the package needs to be started.
# The default policy unless otherwise specified is CONFIGURED_NODE.
# This policy will select nodes in priority order from the list of
# NODE_NAME entries specified below.
# The alternative policy is MIN_PACKAGE_NODE. This policy will select
# the node, from the list of NODE_NAME entries below, which is
# running the least number of packages at the time of failover.
#FAILOVER_POLICY CONFIGURED_NODE
If you use CONFIGURED_NODE as the value for the failover policy, the
package will start up on the highest priority node available in the node
list. When a failover occurs, the package will move to the next highest
priority node in the list that is available.
If you use MIN_PACKAGE_NODE as the value for the failover policy, the
package will start up on the node that is currently running the fewest
other packages. (Note that this does not mean the lightest load; the only
thing that is checked is the number of packages currently running on the
node.)