Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C45CEFFD3 for ; Tue, 19 Mar 2013 22:59:15 +0000 (UTC) Received: (qmail 49322 invoked by uid 500); 19 Mar 2013 22:59:15 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 49281 invoked by uid 500); 19 Mar 2013 22:59:15 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 49270 invoked by uid 99); 19 Mar 2013 22:59:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 22:59:15 +0000 Date: Tue, 19 Mar 2013 22:59:15 +0000 (UTC) From: "Joel Koshy (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (KAFKA-817) Implement a zookeeper path-based controlled shutdown tool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Joel Koshy created KAFKA-817: -------------------------------- Summary: Implement a zookeeper path-based controlled shutdown tool Key: KAFKA-817 URL: https://issues.apache.org/jira/browse/KAFKA-817 Project: Kafka Issue Type: Bug Components: controller, tools Affects Versions: 0.8 Reporter: Joel Koshy Assignee: Neha Narkhede The controlled shutdown tool currently depends on jmxremote.port being exposed. Apparently, this is often not exposed in production environments and makes the script unusable. We can move to a zk-based approach in which the controller watches a path that lists shutting down brokers. This will also make it consistent with the pattern used in some of the other replication-related tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira