Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Wed, 2 Jan 2013 19:42:13 +0000 (UTC)
From: "Joel Koshy (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12623441.1355254655150.70591.1357155733012@arcas>
In-Reply-To: <JIRA.12623441.1355254655150@arcas>
References: <JIRA.12623441.1355254655150@arcas>
Subject: [jira] [Updated] (KAFKA-668) Controlled shutdown admin tool should
 not require controller JMX url/port to be supplied
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/KAFKA-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Koshy updated KAFKA-668:
-----------------------------

    Attachment: KAFKA-668-v2.patch

Needed a rebase.
                
> Controlled shutdown admin tool should not require controller JMX url/port to be supplied
> ----------------------------------------------------------------------------------------
>
>                 Key: KAFKA-668
>                 URL: https://issues.apache.org/jira/browse/KAFKA-668
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8, 0.8.1
>            Reporter: Joel Koshy
>             Fix For: 0.8
>
>         Attachments: KAFKA-668-v1.patch, KAFKA-668-v2.patch
>
>
> The controlled shutdown admin command takes a zookeeper string and also requires the user to supply the controller's jmx url/port. This is a bit annoying since the purpose of the zookeeper string is to discover the controller. The tool should require exactly one of these options. If zookeeper is supplied then discover the controller and its jmx port (which means we will need to add the jmx port information to zk).

--
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