OCF_PACEMAKER_HEALTH(7)
π©Ί ocf_pacemaker_HealthIOWait β the OCF_PACEMAKER_HEALTH(7) page, bestie edition β¨
okay so this is OCF_PACEMAKER_HEALTH(7) from the Pacemaker Configuration manual, and it's literally the glow-up guide for ocf_pacemaker_HealthIOWait. it's a system health agent, it's giving "i'm watching your CPU's vibes", and yes we're gonna read the whole thing together π«Ά
πΈ NAME πΈ
ocf_pacemaker_HealthIOWait β system health based on CPU iowait measurement. that's the whole vibe. it measures, it reports, it slays π
π SYNOPSIS π
[OCF_RESKEY_state=string] [OCF_RESKEY_yellow_limit=integer]
[OCF_RESKEY_red_limit=integer] [OCF_RESKEY_dampening=string]
HealthIOWait [start | stop | monitor | reload-agent | meta-data |
validate-all]
like, you can set those params up front, and then you pick one of those actions: start, stop, monitor, reload-agent, meta-data, or validate-all. pick your fighter π
π¦ DESCRIPTION π¦
okay so it's a system health agent, and what it does is measure the CPU iowait via top and then update the #health-iowait attribute. that's it, that's the whole job. it's not doing the most, it's just doing its thing and telling everyone how the CPU is feeling. main character energy but make it monitoring π
β¨ SUPPORTED PARAMETERS β¨
four params, all iconic, let's go:
OCF_RESKEY_state= string [/health-iowait-.state] β the state file πΎ this is the location where the resource state gets stored.OCF_RESKEY_yellow_limit= integer [10] β upper limit for the yellow health attribute π this is the upper limit of iowait percentage that switches the health attribute to yellow. i.e.#health-iowaitwill go yellow if the%iowaitof the CPU gets higher than10%. it's the "hmm bestie are you okay" threshold.OCF_RESKEY_red_limit= integer [15] β upper limit for red health attribute π¨ this is the upper limit of iowait percentage that switches the health attribute to red. i.e.#health-iowaitwill go red if the%iowaitof the CPU get higher than15%. (yes, the original says "get higher", we're keeping it, it's canon.) this is the "BESTIE NO" threshold. no cap.OCF_RESKEY_dampening= string [5s] β the time to wait (dampening) in seconds for further changes before writing β³ yep, that's the description: the time to wait (dampening) in seconds for further changes before writing. it's said twice in the original and honestly? it's said twice here too. it's that important. it's like a little "chill, let it settle" moment before anything gets written down π
real talk: these limits are percentages, so like, don't go putting100000in there and expecting magic. the defaults are10and15,5sof dampening, and the state lives at/health-iowait-.state. keep those exact, they're load-bearing π
π AUTHOR π
Andrew Beekhof <andrew@beekhof.net> β author. thank you for your service, king π«‘β¨
okay that's the whole page!! and for the cute sign-off: this gem is from the Pacemaker Configuration manual, dated 09/17/2026, and it's page OCF_PACEMAKER_HEALTH(7) ofc. go forth and monitor your iowait responsibly, bestie πππ
π¦ where this page comes from
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms