mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
doc: clarify failover behaviour when node priority is zero
Make it clear the node will not be promoted under any circumstances.
This commit is contained in:
@@ -345,14 +345,18 @@
|
|||||||
</indexterm>
|
</indexterm>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Indicates a preferred priority (default: <literal>100</literal>) for promoting nodes;
|
Indicates a preferred priority (default: <literal>100</literal>) for promoting nodes.
|
||||||
a value of zero prevents the node being promoted to primary.
|
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Note that the priority setting is only applied if two or more nodes are
|
Note that the priority setting is only applied if two or more nodes are
|
||||||
determined as promotion candidates; in that case the node with the
|
determined as promotion candidates; in that case the node with the
|
||||||
higher priority is selected.
|
higher priority is selected.
|
||||||
</para>
|
</para>
|
||||||
|
<para>
|
||||||
|
A value of zero will always prevent the node being promoted to primary, even if there
|
||||||
|
is no other promotion candidate.
|
||||||
|
</para>
|
||||||
|
|
||||||
</listitem>
|
</listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user