[
https://issues.apache.org/jira/browse/KAFKA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621847#comment-13621847
]
Swapnil Ghike commented on KAFKA-330:
-------------------------------------
Thanks for the excellent explanation. Some of these zk operations will not be
repeated for every topic, for example, ZkUtils.getAllBrokersInCluster(zkClient)
or removeFromTopicsBeingDeleted. But anyways, it seems that the cost of ZK
operations is even worse because removeReplicaFromIsr() makes 2 Zk operations
for each replica, which would be responsible for 2*50*8*3(repl-factor) = 2400
zk operations.
I agree with you, let's optimize this after log deletion works correctly.
Similarly, preferred replica election will suffer from a very high number of zk
operations since the callbacks will elect leader for every partition. So, we
could relinquish the lock in preferred replica election too.
> Add delete topic support
> -------------------------
>
> Key: KAFKA-330
> URL: https://issues.apache.org/jira/browse/KAFKA-330
> Project: Kafka
> Issue Type: Bug
> Components: controller, log, replication
> Affects Versions: 0.8
> Reporter: Neha Narkhede
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: features, kafka-0.8, p2, project
> Fix For: 0.8
>
> Attachments: kafka-330-v1.patch
>
>
> One proposal of this API is here -
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+replication+detailed+design+V2#KafkareplicationdetaileddesignV2-Deletetopic
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
