pgpool2.git / summary / log / commit / refs

commit    b1f18e3243ada082c9f862633ca0ddc569a7d89d
Author:   Tatsuo Ishii <ishii@sraoss.co.jp>
Date:     Sun Feb 24 07:46:38 2019 +0000

    Doc: enhance explanation about fail_over command and follow_master command.
    
    Mention that there's complete examples of fail_over_command and
    follow_master_command.


doc.ja/src/sgml/failover.sgml | 29 ++++++++++++++++++++++++++--- doc/src/sgml/failover.sgml | 22 +++++++++++++++++++--- 2 files changed, 45 insertions(+), 6 deletions(-) diff --git a/doc.ja/src/sgml/failover.sgml b/doc.ja/src/sgml/failover.sgml index 6d13053a8..e1f3817fa 100644 --- a/doc.ja/src/sgml/failover.sgml +++ b/doc.ja/src/sgml/failover.sgml @@ -184,6 +184,14 @@ </para> </note> + <para> +<!-- + A complete failover_command example can be found + in <xref linkend="example-cluster">. +--> +failover_commandの完全な例が<xref linkend="example-cluster">にあります。 + </para> + <para> <!-- This parameter can be changed by reloading the <productname>Pgpool-II</> configurations. @@ -473,11 +481,26 @@ </para> </note> <para> -<!-- - Typically <varname>follow_master_command</varname>> command is used to recover - the slave from the new primary by calling the pcp_recovery_node command. +<!-- Typically <varname>follow_master_command</varname> command is + used to recover the slave from the new primary by calling + the pcp_recovery_node command. In + the <varname>follow_master_command</varname>, it is + recommended to check whether + target <productname>PostgreSQL</productname> node is running + or not using pg_ctl since already stopped node usually has a + reason to be stopped: for example, it's broken by hardware + problems or administrator is maintaining the node. If the + node is stopped, skip the node. If the node is running, stop + the node first and recovery it. A + complete <varname>follow_master_command</varname> example + can be found in <xref linkend="example-cluster">. --> 通常は、<varname>follow_master_command</varname>コマンドは<xref linkend="PCP-RECOVERY-NODE">コマンドを呼んで新しいプライマリからスレーブをリカバリするために使用します。 +<varname>follow_master_command</varname>中では、pg_ctlを使ってターゲットの<productname>PostgreSQL</productname>ノードが動いているかどうかを確認することをお勧めします。 +たとえば、そのノードはハードウェア障害で停止しているかも知れませんし、管理者が保守のために停止しているのかも知れません。 +ノードが停止している場合は、そのノードをスキップしてください。 +ノードが動いている場合は、まずそのノードを停止してからリカバリしてください。 +<varname>follow_master_command</varname>の完全な例は、<xref linkend="example-cluster">にあります。 </para> <para> <!-- diff --git a/doc/src/sgml/failover.sgml b/doc/src/sgml/failover.sgml index 204abe5a7..01cc0f564 100644 --- a/doc/src/sgml/failover.sgml +++ b/doc/src/sgml/failover.sgml @@ -136,6 +136,11 @@ </para> </note> + <para> + A complete failover_command example can be found + in <xref linkend="example-cluster">. + </para> + <para> This parameter can be changed by reloading the <productname>Pgpool-II</> configurations. </para> @@ -314,15 +319,26 @@ <para> If <varname>follow_master_command</varname> is not empty, then after failover on the primary node gets completed in Master Slave mode with streaming replication, - <productname>Pgpool-II</productname> degenerates all nodes excepted the new primary + <productname>Pgpool-II</productname> degenerates all nodes except the new primary and starts new child processes to be ready again to accept connections from the clients. After this, <productname>Pgpool-II</productname> executes the command configured in the <varname>follow_master_command</varname> for each degenerated backend nodes. </para> </note> <para> - Typically <varname>follow_master_command</varname> command is used to recover - the slave from the new primary by calling the pcp_recovery_node command. + Typically <varname>follow_master_command</varname> command + is used to recover the slave from the new primary by calling + the pcp_recovery_node command. In + the <varname>follow_master_command</varname>, it is + recommended to check whether + target <productname>PostgreSQL</productname> node is running + or not using pg_ctl since already stopped node usually has a + reason to be stopped: for example, it's broken by hardware + problems or administrator is maintaining the node. If the + node is stopped, skip the node. If the node is running, stop + the node first and recovery it. A + complete <varname>follow_master_command</varname> example + can be found in <xref linkend="example-cluster">. </para> <para> This parameter can be changed by reloading the <productname>Pgpool-II</> configurations. [parent: cf5fe7eb89a1]