From jira-return-11160-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Mon Mar 26 14:51:32 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B4432180649 for ; Mon, 26 Mar 2018 14:51:31 +0200 (CEST) Received: (qmail 54914 invoked by uid 500); 26 Mar 2018 12:51:30 -0000 Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@kafka.apache.org Delivered-To: mailing list jira@kafka.apache.org Received: (qmail 54893 invoked by uid 99); 26 Mar 2018 12:51:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2018 12:51:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E26F1C0EB6 for ; Mon, 26 Mar 2018 12:51:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bQBQwbr3WXWW for ; Mon, 26 Mar 2018 12:51:29 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D6CE36342D for ; Mon, 26 Mar 2018 12:02:01 +0000 (UTC) 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 D7553E0E06 for ; Mon, 26 Mar 2018 12:02:00 +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 3F18C21501 for ; Mon, 26 Mar 2018 12:02:00 +0000 (UTC) Date: Mon, 26 Mar 2018 12:02:00 +0000 (UTC) From: "Uwe Eisele (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-6714) KafkaController marks all Brokers as "Shutting down", though only one broker has been shut down 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-6714?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Eisele updated KAFKA-6714: ------------------------------ Environment: Kafka cluster on Amazon AWS EC2 r4.2xlarge instances with = 5 nodes and a Zookeeper cluster on r4.2xlarge instances with 3 nodes. The c= luster is distributed across 2 availability zones. (was: Kafka Cluster on = Amazon AWS EC2 r4.2xlarge instances with 5 nodes and a Zookeeper Cluster on= r4.2xlarge instances with 3 nodes. The Cluster is distributed across 2 ava= ilability zones.) > KafkaController marks all Brokers as "Shutting down", though only one bro= ker has been shut down > -------------------------------------------------------------------------= ---------------------- > > Key: KAFKA-6714 > URL: https://issues.apache.org/jira/browse/KAFKA-6714 > Project: Kafka > Issue Type: Bug > Components: controller, core > Affects Versions: 0.11.0.2 > Environment: Kafka cluster on Amazon AWS EC2 r4.2xlarge instances= with 5 nodes and a Zookeeper cluster on r4.2xlarge instances with 3 nodes.= The cluster is distributed across 2 availability zones. > Reporter: Uwe Eisele > Priority: Critical > > In our Kafka Cluster we experienced a situation in wich the Kafka control= ler has all Brokers marked as "Shutting down", though indeed only one Broke= r has been shut down. > The last log entry about the broker state before the entry that states th= at all brokers are shutting down states that no brokers are shutting down. > The consequence of this weird state is, that the Kafka controller is not = able to elect any partition leader. > {code:java} > [2018-03-15 16:28:24,288] INFO [Controller 5]: Shutting down broker 5 (ka= fka.controller.KafkaController) > [2018-03-15 16:28:24,288] DEBUG [Controller 5]: All shutting down brokers= : 5 (kafka.controller.KafkaController) > [2018-03-15 16:28:24,288] DEBUG [Controller 5]: Live brokers: 1,2,3,4 (ka= fka.controller.KafkaController) > ... > [2018-03-15 16:28:36,846] INFO [Controller 3]: Currently active brokers i= n the cluster: Set(1, 2, 3, 4) (kafka.controller.KafkaController) > [2018-03-15 16:28:36,846] INFO [Controller 3]: Currently shutting brokers= in the cluster: Set() (kafka.controller.KafkaController) > ... > [2018-03-19 17:57:22,273] INFO [Controller 3]: Shutting down broker 1 (ka= fka.controller.KafkaController) > [2018-03-19 17:57:22,273] DEBUG [Controller 3]: All shutting down brokers= : 1,5,2,3,4 (kafka.controller.KafkaController) > [2018-03-19 17:57:22,273] DEBUG [Controller 3]: Live brokers:=C2=A0 (kafk= a.controller.KafkaController) > ... > [2018-03-19 17:57:22,275] ERROR Controller 3 epoch 83 encountered error w= hile electing leader for partition [zughaltphase_v3_intern_intern_partition= ed_by_evanummer,6] due to: No other replicas in ISR 1,3,5 for [zughaltphase= _v3_intern_intern_partitioned_by_evanummer,6] besides shutting down brokers= 1,5,2,3,4. (state.change.logger)=C2=A0{code} > The question is why the Kafka controller assumes that all brokers are shu= tting down? > The only place in the Kafka code (0.11.0.2) we found in which the shuttin= g down broker set is changed is in the class _kafka.controller.KafkaControl= er_ in line 1407 in the method _doControlledShutdown_. > =C2=A0 > {code:java} > info("Shutting down broker " + id) > if (!controllerContext.liveOrShuttingDownBrokerIds.contains(id)) > throw new BrokerNotAvailableException("Broker id %d does not exist.".fo= rmat(id)) > controllerContext.shuttingDownBrokerIds.add(id) > {code} > However, we should see the log entry "Shutting down broker n" for all Bro= kers in the log file, but it is not there. > =C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)