Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Kafka >> mail # dev >> [jira] [Commented] (KAFKA-705) Controlled shutdown doesn't seem to work on more than one broker in a cluster


Copy link to this message
-
[jira] [Commented] (KAFKA-705) Controlled shutdown doesn't seem to work on more than one broker in a cluster

    [ https://issues.apache.org/jira/browse/KAFKA-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706330#comment-13706330 ]

Jay Kreps commented on KAFKA-705:
---------------------------------

Joel, this is done, no?
                
> Controlled shutdown doesn't seem to work on more than one broker in a cluster
> -----------------------------------------------------------------------------
>
>                 Key: KAFKA-705
>                 URL: https://issues.apache.org/jira/browse/KAFKA-705
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.8
>            Reporter: Neha Narkhede
>            Assignee: Joel Koshy
>            Priority: Critical
>              Labels: bugs
>         Attachments: kafka-705-incremental-v2.patch, kafka-705-v1.patch, shutdown_brokers_eat.py, shutdown-command
>
>
> I wrote a script (attached here) to basically round robin through the brokers in a cluster doing the following 2 operations on each of them -
> 1. Send the controlled shutdown admin command. If it succeeds
> 2. Restart the broker
> What I've observed is that only one broker is able to finish the above successfully the first time around. For the rest of the iterations, no broker is able to shutdown using the admin command and every single time it fails with the error message stating the same number of leaders on every broker.

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