kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Koshy (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-668) Controlled shutdown admin tool should not require controller JMX url/port to be supplied
Date Wed, 02 Jan 2013 22:10:12 GMT

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

Joel Koshy resolved KAFKA-668.
------------------------------

    Resolution: Fixed

Thanks for the review. Committed to 0.8.
                
> 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

Mime
View raw message