You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sönke Liebau (JIRA)" <ji...@apache.org> on 2019/07/30 08:03:00 UTC
[jira] [Resolved] (KAFKA-822) Reassignment of partitions needs a
cleanup
[ https://issues.apache.org/jira/browse/KAFKA-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sönke Liebau resolved KAFKA-822.
--------------------------------
Resolution: Abandoned
Closing this as abandoned after asking for feedback on the dev list. Its probably also fixed, but not absolutely sure of that.
> 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)