From 809061e0024b74f89afdeff8ba83d6514589f417 Mon Sep 17 00:00:00 2001 From: Alan Conway Date: Mon, 24 Mar 2014 20:32:11 +0000 Subject: NO-JIRA: HA doc note that ha-public-url is only needed for amq.failover git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1581038 13f79535-47bb-0310-9956-ffa450edef68 --- .../book/src/cpp-broker/Active-Passive-Cluster.xml | 48 ++++++++-------------- 1 file changed, 18 insertions(+), 30 deletions(-) diff --git a/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml b/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml index 116fd8daef..6cb1b768ab 100644 --- a/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml +++ b/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml @@ -47,7 +47,7 @@ under the License. This approach relies on an external cluster resource manager to detect failures, choose the new primary and handle network partitions. Rgmanager is supported + url="https://fedorahosted.org/cluster/wiki/RGManager">rgmanager is supported initially, but others may be supported in the future.
@@ -81,7 +81,7 @@ under the License. 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 + messages. This is the default behaviour, no options need be set to enable it. For details of client addressing options see "Using the Qpid Messaging API" in Programming in Apache Qpid. @@ -102,7 +102,7 @@ under the License. When a new primary is promoted after a fail-over it is initially in - "recovering" mode. In this mode, it delays acknowledgment of messages + "recovering" mode. In this mode, it delays acknowledgement of messages on behalf of all the backups that were connected to the previous primary. This protects those messages against a failure of the new primary until the backups have a chance to connect and catch up. @@ -277,18 +277,15 @@ ssl_addr = "ssl:" host [":" port]' ha-public-url URL - The URL is advertised to - clients as the "known-hosts" for fail-over. It can be a list or - a single virtual IP address. A virtual IP address is recommended. + This option is only needed for backwards compatibility if you + have been using the amq.failover exchange. + This exchange is now obsolete, it is recommended to use a + virtual IP address instead. - Using this option you can put client and broker traffic on - separate networks, which is recommended. - - - Note: When HA clustering is enabled the broker option - known-hosts-url is ignored and over-ridden by - the ha-public-url setting. + If set, this URL is advertized by the + amq.failover exchange and overrides the + broker option known-hosts-url @@ -426,7 +423,7 @@ NOTE: fencing is not shown, you must configure fencing appropriately for your cl --> - @@ -498,20 +495,17 @@ NOTE: fencing is not shown, you must configure fencing appropriately for your cl The resources section also defines a virtual IP - address for clients. + address for clients: 20.0.20.200. - To take advantage of the virtual IP addresses, qpidd.conf - should contain these lines: + qpidd.conf should contain these lines: ha-cluster=yes - ha-public-url=20.0.10.200 ha-brokers-url=20.0.20.1,20.0.20.2,20.0.20.3 - This configuration allows clients to connect to a single address: - 20.0.10.200. The brokers connect to each other directly via the addresses + The brokers connect to each other directly via the addresses listed in ha-brokers-url. Note the client and broker addresses are on separate sub-nets, this is recommended but not required. @@ -622,10 +616,7 @@ NOTE: fencing is not shown, you must configure fencing appropriately for your cl Clients can only connect to the primary broker. Backup brokers reject any connection attempt by a client. Clients rejected by a backup broker will - automatically fail-over until they connect to the primary. if - ha-public-url contains multiple addresses, the client - will them all in rotation. If it is a virtual IP address the clients will - retry on the same address until it is reconnected. + automatically fail-over until they connect to the primary. Clients are configured with the URL for the cluster (details below for @@ -704,10 +695,10 @@ NOTE: fencing is not shown, you must configure fencing appropriately for your cl Heartbeats are disabled by default. You can enable them by specifying a heartbeat interval (in seconds) for the connection via the heartbeat option. For example: - - qpid::messaging::Connection c("node1,node2,node3","{reconnect:true,heartbeat:10}"); - + + qpid::messaging::Connection c("node1,node2,node3","{reconnect:true,heartbeat:10}"); +
Python clients @@ -886,6 +877,3 @@ NOTE: fencing is not shown, you must configure fencing appropriately for your cl
- - -- cgit v1.2.1