Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improvements for Monitoring fencing devices #400

Merged
merged 3 commits into from
Jul 17, 2024
Merged

Improvements for Monitoring fencing devices #400

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a7a8208
Fix typo
tahliar Jul 12, 2024
dc9a4d3
Improvements for Monitoring fencing devices
tahliar Jul 16, 2024
e20d083
Apply suggestions from editorial review
tahliar Jul 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 7 additions & 15 deletions xml/ha_fencing.xml
View file
Open in desktop
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