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

Broker prematurely accepts TopicMetadataRequests on startup

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      I have an issue where on startup, the broker starts accepting TopicMetadataRequests before it has had metadata sync'd from the controller. This results in a bunch of log entries that look like this:

      013-11-01 03:26:01,577 INFO [kafka-request-handler-0] admin.AdminUtils$ - Topic creation { "partitions":

      { "0":[ 9, 10 ] }

      , "version":1 }
      2013-11-01 03:26:07,767 INFO [kafka-request-handler-1] admin.AdminUtils$ - Topic creation { "partitions":

      { "0":[ 9, 11 ] }

      , "version":1 }
      2013-11-01 03:26:07,823 INFO [kafka-request-handler-1] admin.AdminUtils$ - Topic creation { "partitions":

      { "0":[ 10, 11 ] }

      , "version":1 }
      2013-11-01 03:26:11,183 INFO [kafka-request-handler-2] admin.AdminUtils$ - Topic creation { "partitions":

      { "0":[ 10, 11 ] }

      , "version":1 }

      From an email thread, Neha remarks:

      Before a broker receives the first
      LeaderAndIsrRequest/UpdateMetadataRequest, it is technically not ready to
      start serving any request. But it still ends up serving
      TopicMetadataRequest which can re-create topics accidentally. It shouldn't
      succeed, but this is still a problem.

        Attachments

          Activity

            People

            • Assignee:
              nehanarkhede Neha Narkhede
              Reporter:
              jbrosenberg@gmail.com Jason Rosenberg
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: