Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 1f5b158

Browse files
author
Liudmila Mantrova
committed
DOC: sync doc for scheduler - multimaster support added
1 parent eafcda2 commit 1f5b158

File tree

1 file changed

+27
-7
lines changed

1 file changed

+27
-7
lines changed

doc/src/sgml/pgpro-scheduler.sgml

Lines changed: 27 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -64,13 +64,6 @@
6464
</listitem>
6565
</itemizedlist>
6666

67-
<note>
68-
<para>
69-
<filename>pgpro_scheduler</filename> is not supported for clusters
70-
configured with <xref linkend="multimaster">.
71-
</para>
72-
</note>
73-
7467
<sect2 id="pgpro-scheduler-installation">
7568
<title>Installation and Setup</title>
7669
<para>
@@ -634,6 +627,33 @@ schedule.cancel_job(<replaceable>job_id</replaceable> <type>bigint</type>);
634627
</itemizedlist></para>
635628
<para>To learn more about each function, see <xref linkend="pgpro-scheduler-functions">.</para>
636629
</sect3>
630+
<sect3>
631+
<title>Scheduling Jobs on a Multi-Master Cluster</title>
632+
<para>
633+
Using <filename>pgpro_scheduler</filename>, you can manage
634+
scheduled and one-time jobs on a cluster configured
635+
with <xref linkend="multimaster">.
636+
<filename>pgpro_scheduler</filename> can only manage jobs
637+
on the node on which it is installed. Thus, you must
638+
install and enable <filename>pgpro_scheduler</filename>
639+
on all nodes on which you would like to schedule jobs.
640+
<filename>pgpro_scheduler</filename> instances will manage
641+
jobs on different nodes independently, but the executed jobs
642+
will be replicated to other nodes.
643+
</para>
644+
645+
<para>
646+
Even if you are planning to schedule jobs on a single node only,
647+
it is recommended to enable <filename>pgpro_scheduler</filename>
648+
on several nodes. In this case, if a node with
649+
scheduled jobs fails, another <filename>pgpro_scheduler</filename>
650+
instance picks up these jobs.
651+
If <filename>pgpro_scheduler</filename> is running on more than
652+
one node, the node with the smallest node ID is selected.
653+
The naming pattern of node IDs is defined by the
654+
<xref linkend="pgpro-scheduler-schedule-nodename"> GUC variable.
655+
</para>
656+
</sect3>
637657
</sect2>
638658
<sect2 id="pgpro-scheduler-reference">
639659
<title>Reference</title>

0 commit comments

Comments
 (0)