[
https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206223#comment-14206223
]
Dmitry Pekar edited comment on KAFKA-1753 at 11/11/14 9:58 AM:
---------------------------------------------------------------
[~nehanarkhede] Suppose we have a cluster [0..4] and want to remove broker 2.
This could be archived, for instance, via:
--replace-broker 2 --broker-list 0,1,3,4
The implementation will read all topics/partitions, find those replicas that
are hosted on broker 2 and redistribute them +/- fairly across brokers 0,1,3,4.
This should not affect the replication factor at all.
This approach (using --replace-broker with --broker-list vs using
--decommission-broker) gives us a wider applicability of the command. For
instance, scenarios such as "remove broker 2 and redistribute its replicas
between only broker 0 and 4" could be implemented using this approach.
was (Author: dmitry pekar):
[~nehanarkhede] Suppose we have a cluster [0..4] and want to remove broker 2.
This could be archived, for instance, via:
--replace-broker 2 --broker-list 0,1,3,4
The implementation will read all topics/partitions, find those replicas that
are hosted on broker 2 and redistribute them +/- fairly across brokers 0,1,3,4
This approach (using --replace-broker with --broker-list vs using
--decommission-broker) gives us a wider applicability of the command. For
instance, scenarios such as "remove broker 2 and redistribute its replicas
between only broker 0 and 4" could be implemented using this approach.
> add --decommission-broker option
> --------------------------------
>
> Key: KAFKA-1753
> URL: https://issues.apache.org/jira/browse/KAFKA-1753
> Project: Kafka
> Issue Type: Sub-task
> Components: tools
> Reporter: Dmitry Pekar
> Assignee: Dmitry Pekar
> Fix For: 0.8.3
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
