[ 
https://issues.apache.org/jira/browse/KAFKA-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaobing Fang updated KAFKA-13424:
----------------------------------
    Description: 
In `*TopicDeletionManager.completeDeleteTopic()*`, 
`*controllerContext.removeTopic(topic)*` will be done after deleting topic 
znode in `*client.deleteTopic(topic, controllerContext.epochZkVersion)*`. This 
will trigger `*TopicChangeHandler*`, and process 
`*controllerContext.removeTopic*` again in `*processTopicChange*`. 

It is equivalent to deleting Topic once and executing 
`*controllerContext.removeTopic*` twice. Is this the expected situation?

  was:
In `*TopicDeletionManager.completeDeleteTopic()*`, 
`*controllerContext.removeTopic(topic)*` will be done after deleting topic 
znode in `*client.deleteTopic(topic, controllerContext.epochZkVersion)*`. This 
will trigger `*TopicChangeHandler*`, and process 
`*controllerContext.removeTopic*` aggine in `*processTopicChange*`. 

It is equivalent to deleting Topic once and executing 
`*controllerContext.removeTopic*` twice. Is this the expected situation?


> Redundant cleanup operations in TopicChangeHandler or TopicDeletionManager
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-13424
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13424
>             Project: Kafka
>          Issue Type: Improvement
>          Components: controller
>    Affects Versions: 2.8.0
>            Reporter: Xiaobing Fang
>            Priority: Major
>
> In `*TopicDeletionManager.completeDeleteTopic()*`, 
> `*controllerContext.removeTopic(topic)*` will be done after deleting topic 
> znode in `*client.deleteTopic(topic, controllerContext.epochZkVersion)*`. 
> This will trigger `*TopicChangeHandler*`, and process 
> `*controllerContext.removeTopic*` again in `*processTopicChange*`. 
> It is equivalent to deleting Topic once and executing 
> `*controllerContext.removeTopic*` twice. Is this the expected situation?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to