From users-return-28455-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Mon Aug 8 18:35:54 2011 Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B05908629 for ; Mon, 8 Aug 2011 18:35:54 +0000 (UTC) Received: (qmail 55245 invoked by uid 500); 8 Aug 2011 18:35:54 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 55134 invoked by uid 500); 8 Aug 2011 18:35:53 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 55126 invoked by uid 99); 8 Aug 2011 18:35:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2011 18:35:53 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of tpaulus@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Aug 2011 18:35:48 +0000 Received: from joe.nabble.com ([192.168.236.139]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QqUff-0008Uy-Ev for users@activemq.apache.org; Mon, 08 Aug 2011 11:35:27 -0700 Date: Mon, 8 Aug 2011 11:35:27 -0700 (PDT) From: tpaulus To: users@activemq.apache.org Message-ID: <1312828527453-3727860.post@n4.nabble.com> Subject: gracefully remove broker from cluster MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Suppose I have three brokers in a cluster and clients connected to all three brokers. I want to gracefully remove a broker from the cluster, perhaps for hardware maintenance. I want to do so in such a manner that any client connected to the broker is reconnected to another broker and any messages in the brokers persistent storage are transferred to the persistent storage of another broker. I think I understand that using the failover protocol plus rebalanceClusterClients, updateClusterClients, and updateClusterClientsOnRemove in the broker config will cause clients to reconnect to another broker but I don't see how to move messages from persistent storage to another broker while at the same time preventing new messages from being placed in persistent storage of the broker that I'm taking down. Can anyone provide advice on this use case? -- View this message in context: http://activemq.2283324.n4.nabble.com/gracefully-remove-broker-from-cluster-tp3727860p3727860.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.