This is a bit of a flaw in the topic metadata request logic on the broker
at startup. We need to fix it. 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. Could you file a JIRA?
Thanks,
Neha
On Thu, Oct 31, 2013 at 8:41 PM, Jason Rosenberg <j...@squareup.com> wrote:
> Some times during a rolling restart, I see lots of these messages during
> the restart (these happened in the logs of the 2nd server in the cluster to
> restart (broker 11), after having restarted started, and during the time
> the 3rd node (broker 9) is doing a controlled shutdown before stopping).
>
> Is it creating new topics (it shouldn't have been!). Or is it moving
> topics around, or what?
>
> 2013-11-01 03:25:55,661 INFO [kafka-request-handler-7] admin.AdminUtils$ -
> Topic creation { "partitions":{ "0":[ 9, 11 ] }, "version":1 }
> 2013-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 }
> 20
>
