mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
10425d6967
As they are now XML files. In PostgreSQL itself they remain with the .sgml suffix for backwards compatibility, but that's not important for us.
103 lines
3.2 KiB
XML
103 lines
3.2 KiB
XML
<refentry id="repmgr-witness-unregister" xreflabel="repmgr witness unregister">
|
|
<indexterm>
|
|
<primary>repmgr witness unregister</primary>
|
|
</indexterm>
|
|
|
|
<refmeta>
|
|
<refentrytitle>repmgr witness unregister</refentrytitle>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>repmgr witness unregister</refname>
|
|
<refpurpose>remove a witness node's information to the &repmgr; metadata</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
<para>
|
|
<command>repmgr witness unregister</command> removes a witness server's node
|
|
record from the &repmgr; metadata.
|
|
</para>
|
|
<para>
|
|
The node does not have to be running to be unregistered, however if this is the
|
|
case then either provide connection information for the primary server, or
|
|
execute <command>repmgr witness unregister</command> on a running node and
|
|
provide the parameter <option>--node-id</option> with the node ID of the
|
|
witness server.
|
|
</para>
|
|
<para>
|
|
Execute with the <literal>--dry-run</literal> option to check what would happen
|
|
without actually registering the witness server.
|
|
</para>
|
|
</refsect1>
|
|
<refsect1>
|
|
<title>Examples</title>
|
|
<para>
|
|
Unregistering a running witness node:
|
|
<programlisting>
|
|
$ repmgr -f /etc/repmgr.conf witness unregister
|
|
INFO: connecting to witness node "node3" (ID: 3)
|
|
INFO: unregistering witness node 3
|
|
INFO: witness unregistration complete
|
|
DETAIL: witness node with UD 3 successfully unregistered</programlisting>
|
|
</para>
|
|
<para>
|
|
Unregistering a non-running witness node:
|
|
<programlisting>
|
|
$ repmgr -f /etc/repmgr.conf witness unregister -h node1 -p 5501 -F
|
|
INFO: connecting to node "node3" (ID: 3)
|
|
NOTICE: unable to connect to node "node3" (ID: 3), removing node record on cluster primary only
|
|
INFO: unregistering witness node 3
|
|
INFO: witness unregistration complete
|
|
DETAIL: witness node with id ID 3 successfully unregistered</programlisting>
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Notes</title>
|
|
<para>
|
|
This command will not make any changes to the witness node itself and will neither
|
|
remove any data from the witness database nor stop the PostgreSQL instance.
|
|
</para>
|
|
<para>
|
|
A witness node which has been unregistered, can be re-registered with
|
|
<link linkend="repmgr-witness-register">repmgr witness register --force</link>.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
|
|
<title>Options</title>
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
<term><option>--dry-run</option></term>
|
|
<listitem>
|
|
<para>
|
|
Check prerequisites but don't actually unregister the witness.
|
|
</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
<varlistentry>
|
|
<term><option>--node-id</option></term>
|
|
<listitem>
|
|
<para>
|
|
Unregister witness server with the specified node ID.
|
|
</para>
|
|
</listitem>
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
</refsect1>
|
|
|
|
|
|
<refsect1 id="repmgr-witness-unregister-events">
|
|
<title>Event notifications</title>
|
|
<para>
|
|
A <literal>witness_unregister</literal> <link linkend="event-notifications">event notification</link> will be generated.
|
|
</para>
|
|
</refsect1>
|
|
|
|
</refentry>
|