github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-27 00:46:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

doc: update "connection_check_type" descriptions

Browse Source
This commit is contained in:
Ian Barwick
2019-03-14 15:42:19 +09:00
parent 9347d34ce0
commit 4251590833
2 changed files with 43 additions and 35 deletions
Download Patch File Download Diff File Expand all files Collapse all files

63
doc/appendix-release-notes.sgml
View File

@@ -24,15 +24,15 @@
<important> <important>
<para> <para>
On Debian-based systems, including Ubuntu, if using <application>repmgrd</application> On Debian-based systems, including Ubuntu, if using <application>repmgrd</application>
please ensure that in the file <filename>/etc/init.d/repmgrd</filename>, the parameter please ensure that in the file <filename>/etc/init.d/repmgrd</filename>, the parameter
<varname>REPMGRD_OPTS</varname> contains &quot;<literal>--daemonize=false</literal>&quot;, e.g.: <varname>REPMGRD_OPTS</varname> contains &quot;<literal>--daemonize=false</literal>&quot;, e.g.:
<programlisting> <programlisting>
# additional options # additional options
REPMGRD_OPTS="--daemonize=false"</programlisting> REPMGRD_OPTS="--daemonize=false"</programlisting>
</para> </para>
<para> <para>
For further details, see <link linkend="repmgrd-configuration-debian-ubuntu">repmgrd configuration on Debian/Ubuntu</link>. For further details, see <link linkend="repmgrd-configuration-debian-ubuntu">repmgrd configuration on Debian/Ubuntu</link>.
</para> </para>
</important> </important>
@@ -99,11 +99,11 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
<listitem> <listitem>
<para> <para>
<command><link linkend="repmgr-cluster-show">repmgr cluster show</link></command>: <command><link linkend="repmgr-cluster-show">repmgr cluster show</link></command>:
differentiate between unreachable nodes and nodes which are running but rejecting connections. differentiate between unreachable nodes and nodes which are running but rejecting connections.
</para> </para>
<para> <para>
This makes it possible to see whether a node is unreachable at network level, This makes it possible to see whether a node is unreachable at network level,
or if it is running but rejecting connections for some reason. or if it is running but rejecting connections for some reason.
</para> </para>
</listitem> </listitem>
@@ -152,13 +152,13 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
<listitem> <listitem>
<para> <para>
<application>repmgrd</application> will no longer consider nodes where <application>repmgrd</application> <application>repmgrd</application> will no longer consider nodes where <application>repmgrd</application>
is not running as promotion candidates. is not running as promotion candidates.
</para> </para>
<para> <para>
Previously, if <application>repmgrd</application> was not running on a node, but Previously, if <application>repmgrd</application> was not running on a node, but
that node qualified as the promotion candidate, it would never be promoted due to that node qualified as the promotion candidate, it would never be promoted due to
the absence of a running <application>repmgrd</application>. the absence of a running <application>repmgrd</application>.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@@ -168,7 +168,8 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
</para> </para>
<para> <para>
Possible values are <literal>ping</literal> (default; uses <command>PQping()</command> to Possible values are <literal>ping</literal> (default; uses <command>PQping()</command> to
determine server availability); and <literal>connection</literal> (determines server availability determine server availability), <literal>connection</literal> (attempst to make a new connection to
the upstream node), and <literal>query</literal> (determines server availability
by executing an SQL statement on the node via the existing connection). by executing an SQL statement on the node via the existing connection).
</para> </para>
</listitem> </listitem>
@@ -223,7 +224,7 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
<para> <para>
&repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>, &repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
avoid a potential race condition when comparing received WAL on the standby to the primary's shutdown location, avoid a potential race condition when comparing received WAL on the standby to the primary's shutdown location,
as the standby's walreceiver may not have yet flushed all received WAL to disk. GitHub #518. as the standby's walreceiver may not have yet flushed all received WAL to disk. GitHub #518.
</para> </para>
</listitem> </listitem>
@@ -231,7 +232,7 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
<listitem> <listitem>
<para> <para>
&repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>, &repmgr;: when executing <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
verify the standby (promotion candidate) is currently attached to the primary (demotion candidate). GitHub #519. verify the standby (promotion candidate) is currently attached to the primary (demotion candidate). GitHub #519.
</para> </para>
</listitem> </listitem>
@@ -245,25 +246,25 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
<listitem> <listitem>
<para> <para>
<command><link linkend="repmgr-cluster-show">repmgr cluster show</link></command>: <command><link linkend="repmgr-cluster-show">repmgr cluster show</link></command>:
fix display of node IDs with multiple digits. fix display of node IDs with multiple digits.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
ensure <command><link linkend="repmgr-primary-unregister">repmgr primary unregister</link></command> ensure <command><link linkend="repmgr-primary-unregister">repmgr primary unregister</link></command>
behaves correctly when executed on a witness server. GitHub #548. behaves correctly when executed on a witness server. GitHub #548.
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
<command><link linkend="repmgr-node-check">repmgr node check</link></command> <command><link linkend="repmgr-node-check">repmgr node check</link></command>
will only consider physical replication slots, as the purpose will only consider physical replication slots, as the purpose
of slot checks is to warn about potential issues with of slot checks is to warn about potential issues with
streaming replication standbys which are no longer attached. streaming replication standbys which are no longer attached.
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</para> </para>
@@ -289,15 +290,15 @@ REPMGRD_OPTS="--daemonize=false"</programlisting>
<important> <important>
<para> <para>
On Debian-based systems, including Ubuntu, if using <application>repmgrd</application> On Debian-based systems, including Ubuntu, if using <application>repmgrd</application>
please ensure that the in the file <filename>/etc/init.d/repmgrd</filename>, the parameter please ensure that the in the file <filename>/etc/init.d/repmgrd</filename>, the parameter
<varname>REPMGRD_OPTS</varname> contains &quot;<literal>--daemonize=false</literal>&quot;, e.g.: <varname>REPMGRD_OPTS</varname> contains &quot;<literal>--daemonize=false</literal>&quot;, e.g.:
<programlisting> <programlisting>
# additional options # additional options
REPMGRD_OPTS="--daemonize=false"</programlisting> REPMGRD_OPTS="--daemonize=false"</programlisting>
</para> </para>
<para> <para>
For further details, see <link linkend="repmgrd-configuration-debian-ubuntu">repmgrd daemon configuration on Debian/Ubuntu</link>. For further details, see <link linkend="repmgrd-configuration-debian-ubuntu">repmgrd daemon configuration on Debian/Ubuntu</link>.
</para> </para>
</important> </important>

15
doc/repmgrd-configuration.sgml
View File

@@ -76,9 +76,16 @@
<listitem> <listitem>
<simpara> <simpara>
<literal>connection</literal> - determines server availability <literal>connection</literal> - determines server availability
by attempt ingto make a new connection to the upstream node
</simpara>
</listitem>
<listitem>
<simpara>
<literal>query</literal> - determines server availability
by executing an SQL statement on the node via the existing connection by executing an SQL statement on the node via the existing connection
</simpara> </simpara>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
</para> </para>
</listitem> </listitem>
@@ -92,7 +99,7 @@
<listitem> <listitem>
<para> <para>
The number of attempts (default: <literal>6</literal>) will be made to reconnect to an unreachable The number of attempts (default: <literal>6</literal>) will be made to reconnect to an unreachable
upstream node before initiating a failover. upstream node before initiating a failover.
</para> </para>
<para> <para>
There will be an interval of <option>reconnect_interval</option> seconds between each reconnection There will be an interval of <option>reconnect_interval</option> seconds between each reconnection
@@ -124,7 +131,7 @@
</indexterm> </indexterm>
<term><option>degraded_monitoring_timeout</option></term> <term><option>degraded_monitoring_timeout</option></term>
<listitem> <listitem>
<para> <para>
Interval (in seconds) after which <application>repmgrd</application> will terminate if Interval (in seconds) after which <application>repmgrd</application> will terminate if
either of the servers (local node and or upstream node) being monitored is no longer available either of the servers (local node and or upstream node) being monitored is no longer available
(<link linkend="repmgrd-degraded-monitoring">degraded monitoring mode</link>). (<link linkend="repmgrd-degraded-monitoring">degraded monitoring mode</link>).
@@ -132,8 +139,8 @@
<para> <para>
<literal>-1</literal> (default) disables this timeout completely. <literal>-1</literal> (default) disables this timeout completely.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>