qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From acon...@apache.org
Subject svn commit: r1467008 - in /qpid/branches/0.22/qpid: cpp/README-HA.txt doc/book/src/cpp-broker/Active-Passive-Cluster.xml
Date Thu, 11 Apr 2013 17:53:06 GMT
Author: aconway
Date: Thu Apr 11 17:53:06 2013
New Revision: 1467008

URL: http://svn.apache.org/r1467008
Log:
NO-JIRA: HA doc updates to migration guide and broker book.

Modified:
    qpid/branches/0.22/qpid/cpp/README-HA.txt
    qpid/branches/0.22/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml

Modified: qpid/branches/0.22/qpid/cpp/README-HA.txt
URL: http://svn.apache.org/viewvc/qpid/branches/0.22/qpid/cpp/README-HA.txt?rev=1467008&r1=1467007&r2=1467008&view=diff
==============================================================================
--- qpid/branches/0.22/qpid/cpp/README-HA.txt (original)
+++ qpid/branches/0.22/qpid/cpp/README-HA.txt Thu Apr 11 17:53:06 2013
@@ -79,11 +79,14 @@ will be assumed broken if there is no he
 Configuring rgmanager
 ---------------------
 
-The new HA module requires an external cluster resource manager, `rgmanager`
-provided by the `cman` package.  `rgmanager` is responsible for stopping and
-starting brokers and determining which broker is promoted to primary. It is also
-responsible for detecting primary failures and promoting a new primary.  See
-["Configuring rgmanager as resource manager"][ha-rm-config]
+The new HA module requires an external cluster resource manager.  Initially it
+supports `rgmanager` provided by the `cman` package.  `rgmanager` is responsible
+for stopping and starting brokers and determining which broker is promoted to
+primary. It is also responsible for detecting primary failures and promoting a
+new primary.  See ["Configuring rgmanager as resource manager"][ha-rm-config]
+
+It is relatively easy to integrate with a new resource manager, see
+["Integrating with other Cluster Resource Managers"][ha-other-rm]
 
 Broker Administration Tools
 ---------------------------

Modified: qpid/branches/0.22/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml
URL: http://svn.apache.org/viewvc/qpid/branches/0.22/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml?rev=1467008&r1=1467007&r2=1467008&view=diff
==============================================================================
--- qpid/branches/0.22/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml (original)
+++ qpid/branches/0.22/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml Thu Apr 11
17:53:06 2013
@@ -54,10 +54,16 @@ under the License.
       <title>Avoiding message loss</title>
       <para>
 	In order to avoid message loss, the primary broker <emphasis>delays
-	acknowledgment</emphasis> of messages received from clients until the message has
-	been replicated to and acknowledged by all of the back-up brokers. This means that
-	all <emphasis>acknowledged</emphasis> messages are safely stored on all the
backup
-	brokers.
+	acknowledgment</emphasis> of messages received from clients until the
+	message has been replicated and acknowledged by all of the back-up
+	brokers, or has been consumed from the primary queue.
+      </para>
+      <para>
+	This ensures that all acknowledged messages are safe: they have either
+	been consumed or backed up to all backup brokers.  Messages that are
+	consumed <emphasis>before</emphasis> they are replicated do not need to
+	be replicated. This reduces the work load when replicating a queue with
+	active consumers.
       </para>
       <para>
 	Clients keep <emphasis>unacknowledged</emphasis> messages in a buffer
@@ -82,10 +88,10 @@ under the License.
 	</footnote>
       </para>
       <para>
-	  So if the primary crashes, all the <emphasis>acknowledged</emphasis>
-	  messages will be available on the backup that takes over as the new
-	  primary. The <emphasis>unacknowledged</emphasis> messages will be
-	  re-sent by the clients.  Thus no messages are lost.
+	If the primary crashes, all the <emphasis>acknowledged</emphasis>
+	messages will be available on the backup that takes over as the new
+	primary. The <emphasis>unacknowledged</emphasis> messages will be
+	re-sent by the clients.  Thus no messages are lost.
       </para>
       <para>
 	Note that this means it is possible for messages to be
@@ -177,10 +183,12 @@ under the License.
 	</listitem>
 	<listitem>
 	  <para>
-	    Federated links <emphasis>from</emphasis> the primary will be lost
-	    in fail over, they will not be re-connected to the new
-	    primary. Federation links <emphasis>to</emphasis> the primary will
-	    fail over.
+	    Federation links <emphasis>to</emphasis> the primary will fail over
+	    correctly.  Federated links <emphasis>from</emphasis> the primary
+	    will be lost in fail over, they will not be re-connected to the new
+	    primary. It is possible to work around this by replacing the
+	    <literal>qpidd-primary</literal> start up script with a script that
+	    re-creates federation links when the primary is promoted.
 	  </para>
 	</listitem>
       </itemizedlist>



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org


Mime
View raw message