From 2a347461803f54e39a9b4d41d68a47a06639a0a3 Mon Sep 17 00:00:00 2001 From: Alan Conway Date: Mon, 8 Jun 2015 14:22:35 +0000 Subject: NO-JIRA: Update HA docs to explain how to shut down a primary node. git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1684194 13f79535-47bb-0310-9956-ffa450edef68 --- .../book/src/cpp-broker/Active-Passive-Cluster.xml | 31 ++++++++++++++++++++++ 1 file changed, 31 insertions(+) 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 26d701df64..461b75d320 100644 --- a/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml +++ b/qpid/doc/book/src/cpp-broker/Active-Passive-Cluster.xml @@ -589,6 +589,37 @@ ha-brokers-url=20.0.20.1,20.0.20.2,20.0.20.3 does not start a new broker process, it promotes the existing broker to become the primary. + +
+ Shutting down qpidd on a HA node + + As explained above both the per-node qpidd service + and the re-locatable qpidd-primary service are + implemented by the same qpidd daemon. + + + As a result, stopping the qpidd service will not stop + a qpidd daemon that is acting as primary, and + stopping the qpidd-primary service will not stop a + qpidd process that is acting as backup. + + + To shut down a node that is acting as primary you need to shut down the + qpidd service and relocate the + primary: + + + +clusvcadm -d somenode-qpidd-service +clusvcadm -r qpidd-primary-service + + + + This will shut down the qpidd daemon on that node and + prevent the primary service service from relocating back to the node + because the qpidd service is no longer running there. + +
-- cgit v1.2.1