[
https://issues.apache.org/jira/browse/KAFKA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204782#comment-14204782
]
Dmitry Pekar commented on KAFKA-1753:
-------------------------------------
[~gwenshap] [~nehanarkhede] [~charmalloc]
I was playing with my initial implementation of --replace-broker command and
found that it could be easily generalized to support "delete broker" scenario
without introducing additional UX complexity. IMHO, it should be easy for a
user to understand that to delete broker X he should replace broker X with some
broker Y from the cluster (because the cluster should preserve all partition
replicas located previously on broker X).
So --replace-broker command would cover --decommission-broker scenario. What do
you think about dropping --decommission-broker in favor of
--replace-broker?
> 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)
