Managing HP Serviceguard A.12.00.00 for Linux, June 2014

• pkg1 will consume all of node2's A capacity; no other package that has A weight can run
on this node while pkg1 is running there.
But node2 could still run pkg3 while running pkg1, because pkg3 has no A weight, and
pkg1 is consuming only 15 units (the default) of node2's B capacity, leaving 35 available
to pkg3 (assuming no other package that has B weight is already running there).
• Similarly, if any package that has A weight is already running on node2, pkg1 will not be
able to start there (unless pkg1 has sufficient priority to force another package or packages
to move; see “How Package Weights Interact with Package Priorities and Dependencies”
(page 125)). This is true whenever a package has a weight that exceeds the available amount
of the corresponding capacity on the node.
4.9.10.5 Rules and Guidelines
The following rules and guidelines apply to both the Simple Method (page 119) and the
Comprehensive Method (page 120) of configuring capacities and weights.
• You can define a maximum of four capacities, and corresponding weights, throughout the
cluster.
NOTE: But if you use the reserved CAPACITY_NAME package_limit, you can define
only that single capacity and corresponding weight. See “Simple Method” (page 119).
• Node capacity is defined in the cluster configuration file, via the CAPACITY_NAME and
CAPACITY_VALUE parameters.
• Capacities can be added, changed, and deleted while the cluster is running. This can cause
some packages to be moved, or even halted and not restarted.
• Package weight can be defined in cluster configuration file, via the WEIGHT_NAME and
WEIGHT_DEFAULT parameters, or in the package configuration file, via the weight_name
and weight_value parameters, or both.
• Weights can be assigned (and WEIGHT_DEFAULTs, apply) only to multi-node packages and
to failover packages whose failover_policy (page 188) is configured_node and whose
failback_policy (page 189) is manual.
• If you define weight (weight_name and weight_value) for a package, make sure you
define the corresponding capacity (CAPACITY_NAME and CAPACITY_VALUE) in the cluster
configuration file for at least one node on the package's node_name list (page 186). Otherwise
cmapplyconf will fail when you try to apply the package.
• Weights (both cluster-wide WEIGHT_DEFAULTs, and weights defined in the package
configuration files) can be changed while the cluster is up and the packages are running. This
can cause some packages to be moved, or even halted and not restarted.
4.9.10.6 For More Information
For more information about capacities, see the comments under CAPACITY_NAME and
CAPACITY_VALUE in:
• the cluster configuration file
• the cmquerycl (1m) manpage
• the section “Cluster Configuration Parameters” (page 89) in this manual.
For more information about weights, see the comments under weight_name and weight_value
in:
124 Planning and Documenting an HA Cluster