From: Steve Singer <ssinger@ca.afilias.info>
Date: Thu, 27 Jun 2013 19:29:34 +0000 (-0400)
Subject: documentation updates (FAILOVER)
X-Git-Tag: REL_2_2_0_B5~30
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=74ec8406b74adb96d3f286b13702df876d8e2b6b;p=slony1-engine.git

documentation updates (FAILOVER)
---

diff --git a/doc/adminguide/failover.sgml b/doc/adminguide/failover.sgml
index f40ef2e2..251679af 100644
--- a/doc/adminguide/failover.sgml
+++ b/doc/adminguide/failover.sgml
@@ -265,6 +265,23 @@ they wish to support.
 </para>
 </sect2>
 
+<sect2 id="multiplefailures">
+<title>Multiple Node Failures</title>
+<para>
+If multiple nodes fail at the same time, maybe because an entire data-center has failed,
+then all failed nodes should be passed to the failover command. If we consider a cluster where  node 1 the origin of a set and provides a subscription to
+node 2 and node 3 then node 2 provides a subscription to node 4, what should happen if  both nodes 1 and 2 fail?
+Slony can be told about the failed nodes with the following command
+<programlisting>
+FAILOVER (node=(id=1, backup node=3), node=(id=2, backup node=3));
+</programlisting>
+
+This command requires that a paths exist between node 3 and 4. It will then redirect node 4 to receive the subscription from node 3.
+
+
+</para>
+</sect2>
+
 
 <sect2><title> Automating <command> FAIL OVER </command> </title>
 
diff --git a/doc/adminguide/slonik_ref.sgml b/doc/adminguide/slonik_ref.sgml
index 75d7937f..66b53e83 100644
--- a/doc/adminguide/slonik_ref.sgml
+++ b/doc/adminguide/slonik_ref.sgml
@@ -2683,6 +2683,12 @@ MOVE SET (
 	  <literal>NODE=(ID=val,BACKUP NODE=val), NODE=(ID=val2, BACKUP NODE=val2)</literal> to FAILOVER.
 	</para>
 
+
+	<para>
+	  Nodes that are  forwarding providers can also be passed to the failover command as a failed
+      node.  The failover process will redirect the subscriptions from these nodes to the backup node. 
+	</para>
+
     <variablelist>
      <varlistentry><term><literal> ID = ival </literal></term>
       <listitem><para> ID of the failed node</para></listitem>
diff --git a/doc/adminguide/slony.sgml b/doc/adminguide/slony.sgml
index b57bc0cc..46556df3 100644
--- a/doc/adminguide/slony.sgml
+++ b/doc/adminguide/slony.sgml
@@ -25,9 +25,9 @@
   <!ENTITY funsetdropsequence "<xref linkend= function.setdropsequence-p-seq-id-integer>">
   <!ENTITY funsetmovetable "<xref linkend= function.setmovetable-p-new-set-id-integer-p-tab-id-integer>">
 <!ENTITY funddlscript "<xref linkend=function.ddlscript-complete-p-nodes-text>">
-<!ENTITY fundropnode "<xref linkend=function.dropnode-p-no-id-integer>">
+<!ENTITY fundropnode "<xref linkend=function.dropnode-p-no-ids-integerarray>">
 <!ENTITY funenablenode "<xref linkend=function.enablenode-p-no-id-integer>">
-<!ENTITY funfailednode "<xref linkend=function.failednode-p-backup-node-integer-p-failed-node-integer>">
+<!ENTITY funfailednode "<xref linkend=function.failednode-p-failed-nodes-integer-p-backup-node-integer-p-failed-node-integerarray>">
 <!ENTITY funinitializelocalnode "<xref linkend=function.initializelocalnode-p-comment-integer-p-local-node-id-text>">
 <!ENTITY funlockset "<xref linkend=function.lockset-p-set-id-integer>">
 <!ENTITY funmoveset "<xref linkend=function.moveset-p-new-origin-integer-p-set-id-integer>">