Configure a node health strategy
A node might be functioning well enough to maintain its cluster membership and yet be unhealthy in some respect that makes it an undesirable location for resources. For example, a disk drive might be reporting SMART errors, or the CPU might be highly loaded.
About this task
You can use a node health strategy in Pacemaker to automatically move resources off unhealthy nodes.
You can monitor a node’s health with the following health node resource agents, which set node attributes based on CPU and disk status:
ocf:pacemaker:HealthCPU, which monitors CPU idlingocf:pacemaker:HealthIOWait, which monitors the CPU I/O waitocf:pacemaker:HealthSMART, which monitors SMART status of a disk driveocf:pacemaker:SysInfo, which sets a variety of node attributes with local system information and also functions as a health agent monitoring disk space usage
Additionally, any resource agent might provide node attributes that can be used to define a health node strategy.
The following procedure configures a health node strategy for a cluster that will move resources off of any node whose CPU I/O wait goes above 15%.