You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ac...@apache.org on 2012/10/01 20:22:19 UTC

svn commit: r1392496 - /qpid/trunk/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml

Author: aconway
Date: Mon Oct  1 18:22:19 2012
New Revision: 1392496

URL: http://svn.apache.org/viewvc?rev=1392496&view=rev
Log:
NO-JIRA: HA minor updates to documentation.

Modified:
    qpid/trunk/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml

Modified: qpid/trunk/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml
URL: http://svn.apache.org/viewvc/qpid/trunk/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml?rev=1392496&r1=1392495&r2=1392496&view=diff
==============================================================================
--- qpid/trunk/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml (original)
+++ qpid/trunk/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml Mon Oct  1 18:22:19 2012
@@ -181,18 +181,15 @@ under the License.
     </section>
     <section>
       <title>Limitations</title>
+      <para>
+	There are a number of known limitations in the current preview implementation. These
+	will be fixed in the production versions.
+      </para>
       <itemizedlist>
 	<listitem>
-	  Transactional changes to queue state are not replicated atomically. If the
-	  primary crashes during a transaction, it is possible that the backup could
-	  contain only part of the changes introduced by a transaction.
-	</listitem>
-	<listitem>
-	  Not yet integrated with the persistent store.  A persistent broker must have its
-	  store erased before joining an existing cluster.  If the entire cluster fails,
-	  there are no tools to help identify the most recent store. In the future a
-	  persistent broker will be able to use its stored messages to avoid downloading
-	  messages from the primary when joining a cluster.
+	  Transactional changes to queue state are not replicated atomically. If the primary crashes
+	  during a transaction, it is possible that the backup could contain only part of the
+	  changes introduced by a transaction.
 	</listitem>
 	<listitem>
 	  Configuration changes (creating or deleting queues, exchanges and bindings) are
@@ -209,7 +206,7 @@ under the License.
 	<listitem>
 	  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 can fail over.
+	  <emphasis>to</emphasis> the primary will fail over.
 	</listitem>
       </itemizedlist>
     </section>
@@ -345,6 +342,15 @@ ssl_addr = "ssl:" host [":" port]'
 	      </para>
 	    </entry>
 	  </row>
+	  <row>
+	    <entry><literal>link-heartbeat-interval <replaceable>SECONDS</replaceable></literal></entry>
+	    <entry>
+	      <para>
+		Heartbeat interval for replication links. The link will be assumed broken
+		if there is no heartbeat for twice the interval.
+	      </para>
+	    </entry>
+	  </row>
 	</tbody>
       </tgroup>
     </table>



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