Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Here is the following process to re-produce this issue:
1. Delete a topic using the delete topic request.
2. Confirm the topic is deleted using the list topics request.
3. Create the topic using the create topic request.
In step 3) a race condition can happen that the response returns a TOPIC_ALREADY_EXISTS error code, indicating the topic has already existed.
The root cause of the above issue is in the TopicDeletionManager class:
controller.partitionStateMachine.handleStateChanges(partitionsForDeletedTopic.toSeq, OfflinePartition) controller.partitionStateMachine.handleStateChanges(partitionsForDeletedTopic.toSeq, NonExistentPartition) topicsToBeDeleted -= topic partitionsToBeDeleted.retain(_.topic != topic) kafkaControllerZkUtils.deleteTopicZNode(topic) kafkaControllerZkUtils.deleteTopicConfigs(Seq(topic)) kafkaControllerZkUtils.deleteTopicDeletions(Seq(topic)) controllerContext.removeTopic(topic)
I.e. it first update the broker's metadata cache through the ISR and metadata update request, then delete the topic zk path, and then delete the topic-deletion zk path. However, upon handling the create topic request, the broker will simply try to write to the topic zk path directly. Hence there is a race condition that between brokers update their metadata cache (hence list topic request not returning this topic anymore) and zk path for the topic be deleted (hence the create topic succeed).
The reason this problem could be exposed, is through current handling logic of the create topic response, most of which takes TOPIC_ALREADY_EXISTS as "OK" and moves on, and the zk path will be deleted later, hence leaving the topic to be not created at all:
Looking at the code history, it seems this race condition always exist, but testing on trunk / 1.0 with the above steps it is more likely to happen than before. I wonder if the ZK async calls have an effect here. cc junrao onurkaraman
Attachments
Issue Links
- links to