From 0c394fb5207dfef4077ef562f004e3813764af57 Mon Sep 17 00:00:00 2001 From: Robert Gemmell Date: Sun, 12 Aug 2012 18:54:13 +0000 Subject: QPID-4111: fix issue in the docbook markup to get the PDF generation working again merged change from trunk r1372172 git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/0.18@1372176 13f79535-47bb-0310-9956-ffa450edef68 --- qpid/doc/book/src/java-broker/HA-Guide.xml | 32 +++++++++++++++++++++++------- 1 file changed, 25 insertions(+), 7 deletions(-) diff --git a/qpid/doc/book/src/java-broker/HA-Guide.xml b/qpid/doc/book/src/java-broker/HA-Guide.xml index 429f2f76c2..d3ee43ce1b 100644 --- a/qpid/doc/book/src/java-broker/HA-Guide.xml +++ b/qpid/doc/book/src/java-broker/HA-Guide.xml @@ -26,8 +26,9 @@ under the License. --> -
+
High Availability +
General Introduction The term High Availability (HA) usually refers to having a number of instances of a service such as a Message Broker @@ -40,6 +41,7 @@ some kind of standby state, awaiting to quickly step-in in the event the active node becomes unavailable.
+
HA offerings of the Java Broker The Java Broker's HA offering became available at release 0.18. HA is provided by way of the HA @@ -60,6 +62,7 @@ HA is not currently available for those using the the Derby Store or Memory Message Store.
+
Two Node Cluster
@@ -283,11 +286,13 @@
+
Multi Node Cluster Multi node clusters, that is clusters where the number of nodes is three or more, are not yet ready for use.
+
Configuring a Virtual Host to be a node To configure a virtualhost as a cluster node, configure the virtualhost.xml in the following manner: @@ -385,6 +390,7 @@ ]]>
+
Durability Guarantees The term durability is used to mean that once a @@ -480,6 +486,7 @@
+
Client failover configuration The details about format of Qpid connection URLs can be found at section @@ -495,6 +502,8 @@ amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672?connectdelay='2000'&retries='3';tcp://localhost:5671?connectdelay='2000'&retries='3';tcp://localhost:5673?connectdelay='2000'&retries='3''&failover='roundrobin?cyclecount='30'' ]]>
+ +
Qpid JMX API for HA Qpid exposes the BDB HA store information via its JMX interface and provides APIs to remove a Node from @@ -569,6 +578,7 @@ amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672?connectdelay=' + Mbean <classname>BDBHAMessageStore</classname> operations @@ -592,15 +602,15 @@ amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672?connectdelay=' @@ -632,6 +642,7 @@ System.out.println("Node state:" + state); +
Monitoring cluster In order to discover potential issues with HA Cluster early, all nodes in the Cluster should be monitored on regular basis @@ -704,6 +715,7 @@ Current state of node: Node-5001 from group: TestClusterGroup
+
Disk space requirements Disk space is a critical resource for the HA Qpid broker. @@ -717,6 +729,7 @@ Current state of node: Node-5001 from group: TestClusterGroup Please, make sure to allocate enough space on your disk to avoid this from happening.
+
Network Requirements The HA Cluster performance depends on the network bandwidth, its use by existing traffic, and quality of service. @@ -724,6 +737,7 @@ Current state of node: Node-5001 from group: TestClusterGroup which might include installation of dedicated network hardware on Broker hosts, assigning a higher priority to replication ports, installing a cluster in a separate network not impacted by any other traffic.
+
Security At the moment Berkeley replication API supports only TCP/IP protocol to transfer replication data between Master and Replicas. @@ -731,6 +745,7 @@ Current state of node: Node-5001 from group: TestClusterGroup Also, anyone who can access to this network can introduce a new node and therefore receive a copy of the data. In order to reduce the security risks the entire HA cluster is recommended to run in a separate network protected from general access.
+
Backups In order to protect the entire cluster from some cataclysms which might destroy all cluster nodes, @@ -752,6 +767,7 @@ Current state of node: Node-5001 from group: TestClusterGroup the lifecycle of the cluster.
+
Migration of a non-HA store to HA Non HA stores starting from schema version 4 (0.14 Qpid release) can be automatically converted into HA store on broker startup if replication is first enabled with the DbEnableReplication utility from the BDB JE jar. @@ -782,6 +798,7 @@ java -jar je-&oracleBdbProductVersion;.jar DbEnableReplication -h /path/to/store Due to existing caveats in Berkeley JE with copying of data from Master into Replica it is recommended to restart the Master node after store schema upgrade is finished before starting the Replica nodes.
+
Disaster Recovery This section describes the steps required to restore HA broker cluster from backup. @@ -987,4 +1004,5 @@ java -cp je-&oracleBdbProductVersion;.jar com.sleepycat.je.rep.util.DbResetRepGr With this mode enabled, Qpid broker batches the concurrent transaction commits and syncs transaction data into Master disk in one go. As result, the HA performance only drops by 25-60% for durability NO_SYNC,NO_SYNC,ALL and by 10-90% for WRITE_NO_SYNC,WRITE_NO_SYNC,ALL.
+ -- cgit v1.2.1
updateAddress - + nodeName, name of node, string - - + + newHostName, new host name, string - - + + newPort, new port number, int - + void