kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-155) Support graceful Decommissioning of Broker
Date Wed, 20 Mar 2013 16:21:15 GMT

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

Jun Rao commented on KAFKA-155:
-------------------------------

You mean the partition reassignment tool, not preferred replication election tool, right?
                
> Support graceful Decommissioning of Broker
> ------------------------------------------
>
>                 Key: KAFKA-155
>                 URL: https://issues.apache.org/jira/browse/KAFKA-155
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.7
>            Reporter: Sharad Agarwal
>             Fix For: 0.8
>
>
> 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

Mime
View raw message