diff options
| author | Alan Conway <aconway@apache.org> | 2012-04-16 19:20:15 +0000 |
|---|---|---|
| committer | Alan Conway <aconway@apache.org> | 2012-04-16 19:20:15 +0000 |
| commit | b1b59f31cf7b4b8719e1cdc2ef6c0b6b6eb3843e (patch) | |
| tree | 618d4d8881ec1f53562b9a4ed7c698b98d2ddeb9 /doc | |
| parent | 73fd94ce06996cf01f27de7842eebf6ed2da3e81 (diff) | |
| download | qpid-python-b1b59f31cf7b4b8719e1cdc2ef6c0b6b6eb3843e.tar.gz | |
QPID-3603: Minor improvements to HA tests, documentation and examples.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@1326755 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/book/src/Active-Passive-Cluster.xml | 27 |
1 files changed, 14 insertions, 13 deletions
diff --git a/doc/book/src/Active-Passive-Cluster.xml b/doc/book/src/Active-Passive-Cluster.xml index ffec584679..5f5823bdd2 100644 --- a/doc/book/src/Active-Passive-Cluster.xml +++ b/doc/book/src/Active-Passive-Cluster.xml @@ -316,39 +316,42 @@ under the License. <!-- This is an example of a cluster.conf file to run qpidd HA under rgmanager. This example assumes a 3 node cluster, with nodes named node1, node2 and node3. + +NOTE: fencing is not shown, you must configure fencing appropriately for your cluster. --> <cluster name="qpid-test" config_version="18"> - <!-- The cluster has 3 nodes. Each has a unique nodid and one vote for quorum. --> + <!-- The cluster has 3 nodes. Each has a unique nodid and one vote + for quorum. --> <clusternodes> - <clusternode name="node1" nodeid="1"/> - <clusternode name="node2" nodeid="2"/> - <clusternode name="node3" nodeid="3"/> + <clusternode name="node1.example.com" nodeid="1"/> + <clusternode name="node2.example.com" nodeid="2"/> + <clusternode name="node3.example.com" nodeid="3"/> </clusternodes> <!-- Resouce Manager configuration. --> - <rm log_level="7"> <!-- Verbose logging --> + <rm> <!-- There is a failoverdomain for each node containing just that node. - This lets us stipulate that the qpidd service should always run on all nodes. + This lets us stipulate that the qpidd service should always run on each node. --> <failoverdomains> <failoverdomain name="node1-domain" restricted="1"> - <failoverdomainnode name="node1"/> + <failoverdomainnode name="node1.example.com"/> </failoverdomain> <failoverdomain name="node2-domain" restricted="1"> - <failoverdomainnode name="node2"/> + <failoverdomainnode name="node2.example.com"/> </failoverdomain> <failoverdomain name="node3-domain" restricted="1"> - <failoverdomainnode name="node3"/> + <failoverdomainnode name="node3.example.com"/> </failoverdomain> </failoverdomains> <resources> <!-- This script starts a qpidd broker acting as a backup. --> - <script file="!!sysconfdir!!/init.d/qpidd" name="qpidd"/> + <script file="/etc/init.d/qpidd" name="qpidd"/> <!-- This script promotes the qpidd broker on this node to primary. --> - <script file="!!sysconfdir!!/init.d/qpidd-primary" name="qpidd-primary"/> + <script file="/etc/init.d/qpidd-primary" name="qpidd-primary"/> <!-- This is a virtual IP address for broker replication traffic. --> <ip address="20.0.10.200" monitor_link="1"/> @@ -376,8 +379,6 @@ This example assumes a 3 node cluster, with nodes named node1, node2 and node3. <ip ref="20.0.20.200"/> </service> </rm> - <fencedevices/> - <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/> </cluster> ]]> </programlisting> |