You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Neha Narkhede (JIRA)" <ji...@apache.org> on 2013/11/01 10:53:18 UTC
[jira] [Assigned] (KAFKA-1111) Broker prematurely accepts
TopicMetadataRequests on startup
[ https://issues.apache.org/jira/browse/KAFKA-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neha Narkhede reassigned KAFKA-1111:
------------------------------------
Assignee: Neha Narkhede
> 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
> Assignee: Neha Narkhede
>
> 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)