Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4C39E200D54 for ; Fri, 8 Dec 2017 08:31:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4A996160C1F; Fri, 8 Dec 2017 07:31:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 9207F160BF2 for ; Fri, 8 Dec 2017 08:31:05 +0100 (CET) Received: (qmail 78889 invoked by uid 500); 8 Dec 2017 07:31:04 -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 78875 invoked by uid 99); 8 Dec 2017 07:31:04 -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; Fri, 08 Dec 2017 07:31:04 +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 50F01C1DAF for ; Fri, 8 Dec 2017 07:31:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 CFvIJPfZn6vR for ; Fri, 8 Dec 2017 07:31:03 +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 808185FAC9 for ; Fri, 8 Dec 2017 07:31:03 +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 C3EF6E20C5 for ; Fri, 8 Dec 2017 07:31: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 CBCED273CF for ; Fri, 8 Dec 2017 07:31:00 +0000 (UTC) Date: Fri, 8 Dec 2017 07:31:00 +0000 (UTC) From: "huxihx (JIRA)" To: jira@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-6326) when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 08 Dec 2017 07:31:06 -0000 [ https://issues.apache.org/jira/browse/KAFKA-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283156#comment-16283156 ] huxihx commented on KAFKA-6326: ------------------------------- Based on the screenshot, it seems to be 0.10.2.1 codebase. Did you run into this problem against 1.0.0? > when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout > -------------------------------------------------------------------------------------------------- > > Key: KAFKA-6326 > URL: https://issues.apache.org/jira/browse/KAFKA-6326 > Project: Kafka > Issue Type: Bug > Components: controller > Affects Versions: 1.0.0 > Reporter: HongLiang > Attachments: _f7d1d2b4-39ae-4e02-8519-99bcba849668.png, fast-recver-shutdownbroker.diff > > > when broker is unavailable(such as broker's machine is down), controller will wait 30 sec timeout by dedault. it seems to be that the timeout waiting is not necessary. It will be increase the MTTR of dead broker . -- This message was sent by Atlassian JIRA (v6.4.14#64029)