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 E24AF18558 for ; Mon, 12 Oct 2015 17:09:06 +0000 (UTC) Received: (qmail 89380 invoked by uid 500); 12 Oct 2015 17:09:06 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 89297 invoked by uid 500); 12 Oct 2015 17:09:06 -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 89286 invoked by uid 99); 12 Oct 2015 17:09:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Oct 2015 17:09:06 +0000 Date: Mon, 12 Oct 2015 17:09:06 +0000 (UTC) From: "Ismael Juma (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-1804) Kafka network thread lacks top exception handler MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953391#comment-14953391 ] Ismael Juma commented on KAFKA-1804: ------------------------------------ trunk will be released as 0.9.0.0, see http://search-hadoop.com/m/uyzND1LUUpN1qRojN1 for the discussion thread where the decision was made to name the next release 0.9.0 instead of 0.8.3. > Kafka network thread lacks top exception handler > ------------------------------------------------ > > Key: KAFKA-1804 > URL: https://issues.apache.org/jira/browse/KAFKA-1804 > Project: Kafka > Issue Type: Bug > Components: core > Affects Versions: 0.8.2.0 > Reporter: Oleg Golovin > Priority: Critical > > We have faced the problem that some kafka network threads may fail, so that jstack attached to Kafka process showed fewer threads than we had defined in our Kafka configuration. This leads to API requests processed by this thread getting stuck unresponed. > There were no error messages in the log regarding thread failure. > We have examined Kafka code to find out there is no top try-catch block in the network thread code, which could at least log possible errors. > Could you add top-level try-catch block for the network thread, which should recover network thread in case of exception? -- This message was sent by Atlassian JIRA (v6.3.4#6332)