Skip to content

Commit 51929f1

Browse files
committed
Add formulas for calculating diskless SBD timeouts (#370)
* Add formulas for calculating diskless SBD timeouts bsc#1219972 jsc#DOCTEAM-1289 * Add warning about diskless SBD timeout misconfiguration
1 parent 48664ed commit 51929f1

File tree

1 file changed

+28
-8
lines changed

1 file changed

+28
-8
lines changed

xml/ha_storage_protection.xml

+28-8
Original file line numberDiff line numberDiff line change
@@ -360,8 +360,9 @@
360360
<para>
361361
This timeout is set in the CIB as a global cluster property. If not set
362362
explicitly, it defaults to <literal>0</literal>, which is appropriate for
363-
using SBD with one to three devices. For use of SBD in diskless mode, see <xref
364-
linkend="pro-ha-storage-protect-confdiskless"/> for more details.</para>
363+
using SBD with one to three devices. For SBD in diskless mode, this timeout
364+
must <emphasis>not</emphasis> be <literal>0</literal>. For details, see
365+
<xref linkend="pro-ha-storage-protect-confdiskless"/>.</para>
365366
</listitem>
366367
</varlistentry>
367368
</variablelist>
@@ -1037,7 +1038,9 @@ SBD_WATCHDOG_TIMEOUT=5</screen>
10371038
<screen>&prompt.crm.conf;<command>property stonith-enabled="true"</command><co
10381039
xml:id="co-ha-sbd-stonith-enabled"/>
10391040
&prompt.crm.conf;<command>property stonith-watchdog-timeout=10</command><co
1040-
xml:id="co-ha-sbd-diskless-watchdog-timeout"/></screen>
1041+
xml:id="co-ha-sbd-diskless-watchdog-timeout"/>
1042+
&prompt.crm.conf;<command>property stonith-timeout=15</command><co
1043+
xml:id="co-ha-sbd-diskless-stonith-timeout"/></screen>
10411044
<calloutlist>
10421045
<callout arearefs="co-ha-sbd-stonith-enabled">
10431046
<para>
@@ -1048,12 +1051,29 @@ SBD_WATCHDOG_TIMEOUT=5</screen>
10481051
<callout arearefs="co-ha-sbd-diskless-watchdog-timeout">
10491052
<para>For diskless SBD, this parameter must not equal zero.
10501053
It defines after how long it is assumed that the fencing target has already
1051-
self-fenced. Therefore its value needs to be &gt;= the value of
1052-
<varname>SBD_WATCHDOG_TIMEOUT</varname> in <filename>/etc/sysconfig/sbd</filename>.
1053-
Starting with &productname; 15, if you set <parameter>stonith-watchdog-timeout</parameter>
1054-
to a negative value, Pacemaker will automatically calculate this timeout
1055-
and set it to twice the value of <parameter>SBD_WATCHDOG_TIMEOUT</parameter>.
1054+
self-fenced. Use the following formula to calculate this timeout:
10561055
</para>
1056+
<screen>stonith-watchdog-timeout &gt;= (SBD_WATCHDOG_TIMEOUT * 2)</screen>
1057+
<para>
1058+
If you set <parameter>stonith-watchdog-timeout</parameter>
1059+
to a negative value, Pacemaker automatically calculates this timeout
1060+
and sets it to twice the value of <parameter>SBD_WATCHDOG_TIMEOUT</parameter>.
1061+
</para>
1062+
</callout>
1063+
<callout arearefs="co-ha-sbd-diskless-stonith-timeout">
1064+
<para>
1065+
This parameter must allow sufficient time for fencing to complete.
1066+
For diskless SBD, use the following formula to calculate this timeout:
1067+
</para>
1068+
<screen>stonith-timeout &gt;= stonith-watchdog-timeout + 20%</screen>
1069+
<important>
1070+
<title>Diskless SBD timeouts</title>
1071+
<para>
1072+
With diskless SBD, if the <literal>stonith-timeout</literal> value is smaller than the
1073+
<literal>stonith-watchdog-timeout</literal> value, failed nodes can become stuck
1074+
in an <literal>UNCLEAN</literal> state and block failover of active resources.
1075+
</para>
1076+
</important>
10571077
</callout>
10581078
</calloutlist>
10591079
</step>

0 commit comments

Comments
 (0)