[
https://issues.apache.org/jira/browse/KAFKA-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16888771#comment-16888771
]
Sönke Liebau commented on KAFKA-822:
------------------------------------
While not 100% sure how this looks in today's code, but I do believe that the
/admin/reassign_partitons znode gets deleted after a finished reassignment at
least (see for example KAFKA-6193).
I'd be in favor of closing this due to no activity for more than 6 years.
> Reassignment of partitions needs a cleanup
> ------------------------------------------
>
> Key: KAFKA-822
> URL: https://issues.apache.org/jira/browse/KAFKA-822
> Project: Kafka
> Issue Type: Bug
> Components: controller, tools
> Affects Versions: 0.8.0
> Reporter: Swapnil Ghike
> Assignee: Swapnil Ghike
> Priority: Major
> Labels: bugs
>
> 1. This is probably a left-over from when the ReassignPartitionsCommand used
> to be blocking:
> Currently, for each partition that is reassigned, controller deletes the
> /admin/reassign_partitions zk path, and populates it with a new list with the
> reassigned partition removed from the original list. This is probably an
> overkill, and we can delete the zk path completely once the reassignment of
> all partitions has completed successfully or in error.
> 2. It will help to clarify that there could be no replicas that have started
> and are not in the ISR when KafkaController.onPartitionReassignment() is
> called.
> 3. We should batch the requests in
> KafkaController.StopOldReplicasOfReassignedPartition()
> 4. Update controllerContext.partitionReplicaAssignment only once in
> KafkaController.updateAssignedReplicasForPartition().
> 5. Need to thoroughly test.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
