From dev-return-106148-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Tue Jul 30 08:08:35 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8F5FB180607 for ; Tue, 30 Jul 2019 10:08:35 +0200 (CEST) Received: (qmail 47920 invoked by uid 500); 30 Jul 2019 08:08:33 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 47907 invoked by uid 99); 30 Jul 2019 08:08:33 -0000 Received: from Unknown (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jul 2019 08:08:33 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B1E58E2F82 for ; Tue, 30 Jul 2019 08:08:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id C02C826639 for ; Tue, 30 Jul 2019 08:08:00 +0000 (UTC) Date: Tue, 30 Jul 2019 08:08:00 +0000 (UTC) From: =?utf-8?Q?S=C3=B6nke_Liebau_=28JIRA=29?= To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (KAFKA-1111) Broker prematurely accepts TopicMetadataRequests on startup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-1111?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] S=C3=B6nke Liebau resolved KAFKA-1111. --------------------------------- Resolution: Abandoned Closing as abandoned after no objections on dev list. If this is indeed sti= ll an issue we can always reopen this. > 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 > Priority: Major > > I have an issue where on startup, the broker starts accepting TopicMetada= taRequests before it has had metadata sync'd from the controller. This res= ults 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 (v7.6.14#76016)