Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-4675

Subsequent CreateTopic command could be lost after a DeleteTopic command

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • None

    Description

      This is discovered while investigating KAFKA-3896: If an admin client sends a delete topic command and a create topic command consecutively, even if it wait for the response of the previous command before issuing the second, there is still a race condition that the create topic command could be "lost".

      This is because currently these commands are all asynchronous as defined in KIP-4, and controller will return the response once it has written the corresponding data to ZK path, which can be handled by different listener threads at different paces, and if the thread handling create is faster than the other, the executions could be effectively re-ordered.

      Attachments

        Activity

          People

            Unassigned Unassigned
            guozhang Guozhang Wang
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: