Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9CC8E180C5 for ; Wed, 1 Jul 2015 01:39:54 +0000 (UTC) Received: (qmail 35516 invoked by uid 500); 1 Jul 2015 01:39:54 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 35434 invoked by uid 500); 1 Jul 2015 01:39:54 -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 35419 invoked by uid 99); 1 Jul 2015 01:39:53 -0000 Received: from reviews-vm.apache.org (HELO reviews.apache.org) (140.211.11.40) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 01:39:53 +0000 Received: from reviews.apache.org (localhost [127.0.0.1]) by reviews.apache.org (Postfix) with ESMTP id 02C43AC4C5; Wed, 1 Jul 2015 01:39:53 +0000 (UTC) Content-Type: multipart/alternative; boundary="===============0350571593435951269==" MIME-Version: 1.0 Subject: Re: Review Request 36030: Patch for KAFKA-972 From: "Ashish Singh" To: "kafka" , "Jun Rao" , "Ashish Singh" Date: Wed, 01 Jul 2015 01:39:53 -0000 Message-ID: <20150701013953.13308.90555@reviews.apache.org> X-ReviewBoard-URL: https://reviews.apache.org/ Auto-Submitted: auto-generated Sender: "Ashish Singh" X-ReviewGroup: kafka X-Auto-Response-Suppress: DR, RN, OOF, AutoReply X-ReviewRequest-URL: https://reviews.apache.org/r/36030/ X-Sender: "Ashish Singh" References: <20150630161439.13308.58180@reviews.apache.org> In-Reply-To: <20150630161439.13308.58180@reviews.apache.org> Reply-To: "Ashish Singh" X-ReviewRequest-Repository: kafka --===============0350571593435951269== MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit > On June 30, 2015, 4:14 p.m., Jun Rao wrote: > > Thanks for the patch. A few comments below. > > > > 1. Could you add a unit test for this? > > > > 2. Also, we may have a similar issue when handling the failure of the broker. Currently, the logic in the controller is that the controller will only send an UpdateMetadataRequest to all brokers if a new leader is elected. So, when shutting down a broker with no leaders on it, the controller won't send UpdateMetadataRequest to reflect the shutdown broker. Could you verify if this is indeed an issue? Thanks for the review Jun. Added tests. Yes, (2) is an issue, added fix with test to catch it. - Ashish ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/36030/#review89907 ----------------------------------------------------------- On June 30, 2015, 12:46 a.m., Ashish Singh wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/36030/ > ----------------------------------------------------------- > > (Updated June 30, 2015, 12:46 a.m.) > > > Review request for kafka. > > > Bugs: KAFKA-972 > https://issues.apache.org/jira/browse/KAFKA-972 > > > Repository: kafka > > > Description > ------- > > KAFKA-972: MetadataRequest returns stale list of brokers > > > Diffs > ----- > > core/src/main/scala/kafka/controller/KafkaController.scala 36350579b16027359d237b64699003358704ac6f > > Diff: https://reviews.apache.org/r/36030/diff/ > > > Testing > ------- > > > Thanks, > > Ashish Singh > > --===============0350571593435951269==--