[
https://issues.apache.org/jira/browse/KAFKA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206968#comment-14206968
]
Neha Narkhede commented on KAFKA-1752:
--------------------------------------
Thanks for the update. I agree with the 2 scenarios you mentioned above.
However, shouldn't adding one or more new brokers just evenly transfer existing
partitions off of the cluster to the new nodes? I actually don't think the
--replace-broker <n> --broker-list <x,y,z> is intuitive. All users want is to
add new brokers and have some load transferred to the new brokers. If we add a
strategy to figure that out and let generate output the assignment to
facilitate this operation, it should solve both the problems you listed above.
> 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)
