[
https://issues.apache.org/jira/browse/KAFKA-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233942#comment-16233942
]
Matthias Rampke commented on KAFKA-1506:
----------------------------------------
Related issue with more reasons to cancel: KAFKA-1676
There are lots of reasons one would want to cancel a reassignment, completely
unrelated to bugs in Kafka and purely out of operational considerations (we
decided we don't want to do this after all; the reassignment is hurting cluster
performance too much; the reassignment is to a dead broker). It appears that
the only way to do this is to mess with Zookeeper, or lying about broker IDs
(bringing up a new broker with an old ID).
For me, just cancelling everything that is going on and leaving things where
they are is the right thing to do – one of the reasons to cancel is because the
act of moving things around hurts the cluster, and in that case moving
everything back would be just as bad. I would not expect anything to be moved
back. Just being able to tell Kafka to "stop and hold" would be a significant
improvement, and let operators then re-reassign as needed.
> Cancel "kafka-reassign-partitions" Job
> --------------------------------------
>
> Key: KAFKA-1506
> URL: https://issues.apache.org/jira/browse/KAFKA-1506
> Project: Kafka
> Issue Type: New Feature
> Components: replication, tools
> Affects Versions: 0.8.1, 0.8.1.1
> Reporter: Paul Lung
> Priority: Major
> Labels: newbie++
>
> I started a reassignment, and for some reason it just takes forever. However,
> it won¹t let me start another reassignment job while this one is running. So
> a tool to cancel a reassignment job is needed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
