kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Rosenberg (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-1111) Broker prematurely accepts TopicMetadataRequests on startup
Date Fri, 01 Nov 2013 05:57:17 GMT
Jason Rosenberg created KAFKA-1111:
--------------------------------------

             Summary: Broker prematurely accepts TopicMetadataRequests on startup
                 Key: KAFKA-1111
                 URL: https://issues.apache.org/jira/browse/KAFKA-1111
             Project: Kafka
          Issue Type: Bug
            Reporter: Jason Rosenberg


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.




--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message