This is probably because some metadata requests were issued to a newly
started broker before the controller has propagated the metadata. Since the
broker doesn't have the metadata in the cache, it thinks the topic doesn't
exist and tries to create the topic. The creation will fail though since
it's already registered in ZK. These INFO logging should be transient
though.
Thanks,
Jun
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
>
