You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Maxime Brugidou (JIRA)" <ji...@apache.org> on 2013/01/15 16:10:12 UTC

[jira] [Commented] (KAFKA-155) Support graceful Decommissioning of Broker

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

Maxime Brugidou commented on KAFKA-155:
---------------------------------------

I think this is done in 0.8 branch with the ShutdownBroker admin command (which goes through JMX command KafkController.shutdownBroker())
                
> Support graceful Decommissioning of Broker
> ------------------------------------------
>
>                 Key: KAFKA-155
>                 URL: https://issues.apache.org/jira/browse/KAFKA-155
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Sharad Agarwal
>
> There should be a graceful way of decommissioning the broker so that there is absolutely 0 data loss. Decommissioning is not necessarily related to replication (Kafka-50).
> There should be a way to get the broker out of the cluster only from the produce side. Consumers should be able to continue keep pulling data. When the administrator is sure that all data has been consumed by consumers, broker node can be removed permanently.
> Same would be useful for rolling upgrades without any message loss.

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