From 3c3cd5dd504ed43b684fcfe9ab2ef9b75b8f436f Mon Sep 17 00:00:00 2001 From: Tahlia Richardson <3069029+tahliar@users.noreply.github.com> Date: Thu, 18 Jul 2024 09:59:59 +1000 Subject: [PATCH] Improvements for Monitoring fencing devices (#400) * Fix typo * Improvements for Monitoring fencing devices bsc#1219181 jsc#DOCTEAM-1251 * Apply suggestions from editorial review Co-authored-by: Daria Vladykina --------- Co-authored-by: Daria Vladykina --- xml/ha_fencing.xml | 22 +++++++--------------- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/xml/ha_fencing.xml b/xml/ha_fencing.xml index edc7add1e..6cb59fba9 100644 --- a/xml/ha_fencing.xml +++ b/xml/ha_fencing.xml @@ -295,7 +295,7 @@ resources means loading and unloading the &stonith; device driver on a node. Starting and stopping are thus only administrative operations and do not translate to any operation on the fencing device itself. However, - monitoring does translate to logging it to the device (to verify that the + monitoring does translate to logging in to the device (to verify that the device will work in case it is needed). When a &stonith; resource fails over to another node it enables the current node to talk to the &stonith; device by loading the respective driver. @@ -536,17 +536,6 @@ hostlist monitoring operation for checking status. - - - - Monitoring &stonith; resources - - Monitor &stonith; resources regularly, yet sparingly. For most devices a - monitoring interval of at least 1800 seconds (30 minutes) should - suffice. - - - Fencing devices are an indispensable part of an HA cluster, but the less you need to use them, the better. Power management equipment is often @@ -557,9 +546,12 @@ hostlist - Checking the status of fencing devices once every few hours should - be enough. The probability that a fencing operation needs to be - performed and the power switch fails is low. + The probability that a fencing operation needs to be performed and the + fencing device fails is low. For most devices, a monitoring interval of + at least 1800 seconds (30 minutes) should suffice. The exact value depends + on the device and infrastructure. &stonith; SBD resources do not need a + monitor at all. See and + .