Clicking on the
tab displays the page, which provides an interface for configuring quorum disk parameters if you need to use a quorum disk.
Quorum disk parameters and heuristics depend on the site environment and the special requirements needed. To understand the use of quorum disk parameters and heuristics, see the qdisk(5) man page. If you require assistance understanding and using quorum disk, contact an authorized Red Hat support representative.
parameter is enabled by default. If you need to use a quorum disk, click , enter the quorum disk parameters, and click . You must restart the cluster for the changes to take effect.
Table 4.1. Quorum-Disk Parameters
| || Specifies the quorum disk label created by the |
mkqdisk utility. If this field is used, the quorum daemon reads the
/proc/partitions file and checks for qdisk signatures on every block device found, comparing the label against the specified label. This is useful in configurations where the quorum device name differs among nodes.
| || |
| — The program used to determine if this heuristic is available. This can be anything that can be executed by |
/bin/sh -c. A return value of 0 indicates success; anything else indicates failure. This field is required.
| — The frequency (in seconds) at which the heuristic is polled. The default interval for every heuristic is 2 seconds.|
| — The weight of this heuristic. The default score for each heuristic is 1. |
| — The number of consecutive failures required before this heuristic is declared unavailable. |
| || The minimum score for a node to be considered "alive". If omitted or set to 0, the default function, |
floor((n+1)/2), is used, where n is the sum of the heuristics scores. The value must never exceed the sum of the heuristic scores; otherwise, the quorum disk cannot be available.
) in each cluster node. However, for the quorum disk to operate or for any modifications you have made to the quorum disk parameters to take effect, you must restart the cluster (see Section 5.4, “Starting, Stopping, Restarting, and Deleting Clusters”
), ensuring that you have restarted the
daemon on each node.
on the tab propagates changes to the cluster configuration file (