[
https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209747#comment-14209747
]
Dmitry Pekar commented on KAFKA-1752:
-------------------------------------
[~nehanarkhede]
It is clear for me how to implement --decomission-broker in the context of
partition reassignment.
But it's unclear how to implement partition reassignment for proposed
--add-broker.
Let's suppose that the strategy of reassignment tries to redistribute replicas
fairly by using minimal number of reassignments.
A lot of scenarios exists where it is impossible to do such reassignment.
For instance, consider a cluster with 2 brokers 0 and 1 and topic with 1
partition.
The replica assignment is partition-0 -> [broker-0, broker-1].
If we are going to add broker 2 what we should choose:
- reassign partition 0 replica from broker 0 or 1 leaving it without data?
- leave broker 2 without data?
- change the replication factor of partition 0?
- raise an error that there is no data for broker 2 to assign?
> add --replace-broker option
> ---------------------------
>
> Key: KAFKA-1752
> URL: https://issues.apache.org/jira/browse/KAFKA-1752
> 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)
