[
https://issues.apache.org/jira/browse/KAFKA-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233971#comment-16233971
]
Ismael Juma commented on KAFKA-1676:
------------------------------------
One thing to consider is what to do with the extra replicas that have been
created and haven't caught up yet. Not doing anything about those would mean
that the extra traffic would continue. So, there is a case for stopping the
extra replicas that have not completed yet. In any case, a KIP would be
required.
> Ability to cancel replica reassignment in progress
> --------------------------------------------------
>
> Key: KAFKA-1676
> URL: https://issues.apache.org/jira/browse/KAFKA-1676
> Project: Kafka
> Issue Type: New Feature
> Components: controller
> Affects Versions: 0.8.1.1
> Reporter: Ryan Berdeen
> Priority: Major
> Labels: newbie
>
> I've had several situations where I have started a replica reassignment that
> I've needed to cancel before it completed.
> This has happened
> * when moving to a new broker that turns out to be running on an impaired
> server
> * if the extra replication hurts cluster performance
> * dealing with replication bugs in kafka, like KAFKA-1670
> * when a single replica reassignment is taking a long time, and I want to
> start more replica assignments without waiting for the current one to finish.
> For the first three cases, as a last resort I have deleted the
> {{/admin/reassign_partitions}} key from ZooKeeper and restarted the
> controller. I would like to be able to do this by signaling the controller to
> stop, and to leave the list of assignments as they exist at that moment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
