[
https://issues.apache.org/jira/browse/KAFKA-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160783#comment-14160783
]
Neha Narkhede commented on KAFKA-1678:
--------------------------------------
What is the purpose of replace replica? If the only purpose is to move the
broker from one faulty machine to another, you could just restart a broker with
the same broker.id. Decommission a broker is more useful as Kafka would have to
evenly distribute the replicas on the broker being decommissioned onto other
brokers in the cluster. It's also worth thinking how this change would affect
the rest of the user experience when using the reassign partitions command.
Today, the way it's designed is that there are multiple options to generate a
replica assignment and the one way to execute it. It's not very intuitive,
though that change is bigger and hence probably deserves it's own JIRA.
Presumably, you are suggesting add another option for generating an assignment?
> add new options for reassign partition to better manager dead brokers
> ---------------------------------------------------------------------
>
> Key: KAFKA-1678
> URL: https://issues.apache.org/jira/browse/KAFKA-1678
> Project: Kafka
> Issue Type: Bug
> Reporter: Joe Stein
> Assignee: Gwen Shapira
> Labels: operations
> Fix For: 0.8.3
>
>
> this is in two forms
> --replace-replica
> which is from broker.id to broker.id
> and
> --remove-replica
> which is just a single broker.id
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
