Skip to content

Commit

Permalink
Improvements for Monitoring fencing devices (#400)
Browse files Browse the repository at this point in the history
* Fix typo

* Improvements for Monitoring fencing devices

bsc#1219181
jsc#DOCTEAM-1251

* Apply suggestions from editorial review

Co-authored-by: Daria Vladykina <[email protected]>

---------

Co-authored-by: Daria Vladykina <[email protected]>
  • Loading branch information
tahliar and dariavladykina authored Jul 17, 2024
1 parent ec529d4 commit c85509c
Showing 1 changed file with 7 additions and 15 deletions.
22 changes: 7 additions & 15 deletions xml/ha_fencing.xml
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -536,17 +536,6 @@ hostlist</screen>
monitoring operation for checking status.
</para>

<!--fate#310010-->

<note>
<title>Monitoring &stonith; resources</title>
<para>
Monitor &stonith; resources regularly, yet sparingly. For most devices a
monitoring interval of at least 1800 seconds (30 minutes) should
suffice.
</para>
</note>

<para>
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
Expand All @@ -557,9 +546,12 @@ hostlist</screen>
</para>

<para>
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 <xref linkend="sec-ha-fencing-special"/> and
<xref linkend="cha-ha-storage-protect"/>.
</para>

<para>
Expand Down

0 comments on commit c85509c

Please sign in to comment.