diff options
| author | Alan Conway <aconway@apache.org> | 2012-03-27 20:32:18 +0000 |
|---|---|---|
| committer | Alan Conway <aconway@apache.org> | 2012-03-27 20:32:18 +0000 |
| commit | 73886cfd6278d7ea0da1b18cd439481d88938197 (patch) | |
| tree | 8ed4749260ad03d50e6f6c2610723ec08120fb02 /qpid/cpp/etc/cluster.conf-example.xml.in | |
| parent | d1a5ccad56bbddb4063e07f88ba16480232246e9 (diff) | |
| download | qpid-python-73886cfd6278d7ea0da1b18cd439481d88938197.tar.gz | |
QPID-3603: Substitute installation directories in qpidd init scripts.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1306007 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'qpid/cpp/etc/cluster.conf-example.xml.in')
| -rw-r--r-- | qpid/cpp/etc/cluster.conf-example.xml.in | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/qpid/cpp/etc/cluster.conf-example.xml.in b/qpid/cpp/etc/cluster.conf-example.xml.in new file mode 100644 index 0000000000..dbeb3af537 --- /dev/null +++ b/qpid/cpp/etc/cluster.conf-example.xml.in @@ -0,0 +1,69 @@ +<?xml version="1.0"?> +<!-- +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. +--> + +<cluster name="qpid-test" config_version="18"> + <!-- 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"/> + </clusternodes> + <!-- Resouce Manager configuration. + TODO explain central_processing="1" + --> + <rm log_level="7" central_processing="1"> + <!-- + 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. + --> + <failoverdomains> + <failoverdomain name="node1-domain" restricted="1"> + <failoverdomainnode name="node1"/> + </failoverdomain> + <failoverdomain name="node2-domain" restricted="1"> + <failoverdomainnode name="node2"/> + </failoverdomain> + <failoverdomain name="node3-domain" restricted="1"> + <failoverdomainnode name="node3"/> + </failoverdomain> + </failoverdomains> + + <resources> + <!-- This script starts a qpidd broker acting as a backup. --> + <script file="!!sysconfdir!!/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"/> + + <!-- This is a virtual IP address for broker replication traffic. --> + <ip address="20.0.10.200" monitor_link="1"/> + + <!-- This is a virtual IP address on a seprate network for client traffic. --> + <ip address="20.0.20.200" monitor_link="1"/> + </resources> + + <!-- There is a qpidd service on each node, it should be restarted if it fails. --> + <service name="node1-qpidd-service" domain="node1-domain" recovery="restart"> + <script ref="qpidd"/> + </service> + <service name="node2-qpidd-service" domain="node2-domain" recovery="restart"> + <script ref="qpidd"/> + </service> + <service name="node3-qpidd-service" domain="node3-domain" recovery="restart"> + <script ref="qpidd"/> + </service> + + <!-- There should always be a single qpidd-primary service, it can run on any node. --> + <service name="qpidd-primary-service" autostart="1" exclusive="0" recovery="relocate"> + <script ref="qpidd-primary"/> + <!-- The primary has the IP addresses for brokers and clients. --> + <ip ref="20.0.10.200"/> + <ip ref="20.0.20.200"/> + </service> + </rm> + <fencedevices/> + <fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/> +</cluster> |