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/07/16 19:00:28 UTC
svn commit: r1362135 -
/qpid/branches/0.18/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml
Author: aconway
Date: Mon Jul 16 17:00:28 2012
New Revision: 1362135
URL: http://svn.apache.org/viewvc?rev=1362135&view=rev
Log:
NO-JIRA: Minor documentation updates.
Modified:
qpid/branches/0.18/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml
Modified: qpid/branches/0.18/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml
URL: http://svn.apache.org/viewvc/qpid/branches/0.18/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml?rev=1362135&r1=1362134&r2=1362135&view=diff
==============================================================================
--- qpid/branches/0.18/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml (original)
+++ qpid/branches/0.18/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml Mon Jul 16 17:00:28 2012
@@ -90,7 +90,17 @@ under the License.
</para>
<para>
Clients buffer unacknowledged messages and re-send them in the event of
- a fail-over. If the primary crashes before a message is replicated to
+ a fail-over.
+ <footnote>
+ <para>
+ Clients must use 'at-least-once' reliability to enable re-send of
+ unacknowledged messages. This is the default behavior, no options
+ need be set to enable it. For details of client addressing options see
+ "Using the Qpid Messaging API" in <citetitle>Programming in Apache
+ Qpid</citetitle>
+ </para>
+ </footnote>
+ If the primary crashes before a message is replicated to
all the backups, the client will re-send the message when it fails over
to the new primary.
</para>
@@ -494,10 +504,11 @@ NOTE: fencing is not shown, you must con
<section>
<title>Broker Administration Tools</title>
<para>
- Normally, clients are not allowed to connect to a backup broker. However management tools are
- allowed to connect to a backup brokers. If you use these tools you <emphasis>must
- not</emphasis> add or remove messages from replicated queues, or delete replicated queues or
- exchanges as this will corrupt the replication process and may cause message loss.
+ Normally, clients are not allowed to connect to a backup broker. However
+ management tools are allowed to connect to a backup brokers. If you use
+ these tools you <emphasis>must not</emphasis> add or remove messages from
+ replicated queues, nor create or delete replicated queues or exchanges as
+ this will disrupt the replication process and may cause message loss.
</para>
<para>
<command>qpid-ha</command> allows you to view and change HA configuration settings.
@@ -600,10 +611,12 @@ NOTE: fencing is not shown, you must con
membership.
</para>
<para>
- Suppose your cluster has 3 nodes: <literal>node1</literal>, <literal>node2</literal>
- and <literal>node3</literal> all using the default AMQP port. To connect a client you
- need to specify the address(es) and set the <literal>reconnect</literal> property to
- <literal>true</literal>. Here's how to connect each type of client:
+ Suppose your cluster has 3 nodes: <literal>node1</literal>,
+ <literal>node2</literal> and <literal>node3</literal> all using the
+ default AMQP port, and you are not using a virtual IP address. To connect
+ a client you need to specify the address(es) and set the
+ <literal>reconnect</literal> property to <literal>true</literal>. The
+ following sub-sections show how to connect each type of client.
</para>
<section>
<title>C++ clients</title>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org