pgpool2.git / summary / log / commit / refs
commit 530d8220fd8d191b013dc8cf490413a626cf3fd0
Author: Tatsuo Ishii <ishii@postgresql.org>
Date: Thu Feb 09 09:11:04 2017 +0000
Enhance document.
Add note about %m in failover command. Add indexes to "streaming
replication mode", "master slave mode" and "native replication mode".
doc/src/sgml/failover.sgml | 35 +++++++++++++++++++++++++++++++++--
doc/src/sgml/runtime.sgml | 12 ++++++++++++
2 files changed, 45 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/failover.sgml b/doc/src/sgml/failover.sgml
index fe86da2c3..97f81c79e 100644
--- a/doc/src/sgml/failover.sgml
+++ b/doc/src/sgml/failover.sgml
@@ -82,16 +82,47 @@
</tgroup>
</table>
+ <note>
+ <para>
+ The "master node" referes to a node which has the
+ "youngest (or the smallest) node id" among live the
+ database nodes. In <link linkend="running-mode">streaming
+ replication mode</link>, this may be different from
+ primary node. In <xref linkend="failover-command-table">,
+ %m is the new master node chosen
+ by <productname>Pgpool-II</productname>. It is the node
+ being assigned the youngest (smallest) node id which is
+ alive. For example if you have 3 nodes, namely node 0, 1,
+ 2. Suppose node 1 the primary and all of them are healthy
+ (no down node). If node 1 fails, failover_command is
+ called with %m = 0.
+ </para>
+ </note>
+
<note>
<para>
- When a failover is performed, <productname>Pgpool-II</productname> kills all
- its child processes, which will in turn terminate all the active sessions to
+ When a failover is performed,
+ basically <productname>Pgpool-II</productname> kills all
+ its child processes, which will in turn terminate all the
+ active sessions to
<productname>Pgpool-II</productname>. After that <productname>Pgpool-II</productname>
invokes the <command>failover_command</command> and after the command completion
<productname>Pgpool-II</productname> starts new child processes
which makes it ready again to accept client connections.
</para>
+ <para>
+ However from <productname>Pgpool-II</productname> 3.6, In
+ the steaming replication mode, client sessions will not be
+ disconnected when a fail-over occurs any more if the
+ session does not use the failed standby server. If the
+ primary server goes down, still all sessions will be
+ disconnected. Health check timeout case will also cause
+ the full session disconnection. Other health check error,
+ including retry over case does not trigger full session
+ disconnection.
+ </para>
</note>
+
<para>
This parameter can be changed by reloading the <productname>Pgpool-II</> configurations.
</para>
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 77facce35..16f9afe10 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -111,6 +111,18 @@ password: <userinput>your_password</userinput>
<sect2 id="running-mode">
<title>Running mode of Pgpool-II</title>
+ <indexterm zone="running-mode">
+ <primary>streaming replication mode</primary>
+ </indexterm>
+
+ <indexterm zone="running-mode">
+ <primary>master slave mode</primary>
+ </indexterm>
+
+ <indexterm zone="running-mode">
+ <primary>native replication mode</primary>
+ </indexterm>
+
<para>
There are four different running modes in <productname>Pgpool-II</>: streaming
replication mode, master slave mode, native replication mode and
[parent: 816c8474143b]