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 9BC78200C16 for ; Thu, 9 Feb 2017 18:33:47 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 9A633160B6E; Thu, 9 Feb 2017 17:33:47 +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 E4E7A160B50 for ; Thu, 9 Feb 2017 18:33:46 +0100 (CET) Received: (qmail 28678 invoked by uid 500); 9 Feb 2017 17:33:45 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 28497 invoked by uid 99); 9 Feb 2017 17:33:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Feb 2017 17:33:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 52E641A04DD for ; Thu, 9 Feb 2017 17:33:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id rbWeimxFQ2Mh for ; Thu, 9 Feb 2017 17:33:44 +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 0B2F55FDF3 for ; Thu, 9 Feb 2017 17:33:44 +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 D6AB8E059C for ; Thu, 9 Feb 2017 17:33:42 +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 F1E6421D6A for ; Thu, 9 Feb 2017 17:33:41 +0000 (UTC) Date: Thu, 9 Feb 2017 17:33:41 +0000 (UTC) From: "Hudson (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14034) Allow ipc layer exceptions to selectively close connections MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 09 Feb 2017 17:33:47 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859861#comment-15859861 ] Hudson commented on HADOOP-14034: --------------------------------- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11226 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11226/]) HADOOP-14034. Allow ipc layer exceptions to selectively close (kihwal: rev b6bb99c18a772d2179d5cc6757cddf141e8d39c0) * (edit) hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java * (edit) hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/ipc/TestRPC.java > Allow ipc layer exceptions to selectively close connections > ----------------------------------------------------------- > > Key: HADOOP-14034 > URL: https://issues.apache.org/jira/browse/HADOOP-14034 > Project: Hadoop Common > Issue Type: Sub-task > Components: ipc > Affects Versions: 2.7.0 > Reporter: Daryn Sharp > Assignee: Daryn Sharp > Fix For: 2.8.1, 3.0.0-alpha3 > > Attachments: HADOOP-14034-branch-2.patch, HADOOP-14034-trunk.patch > > > IPC layer exceptions generated in the readers are translated into fatal errors - resulting in connection closure. Ex. RetriableExceptions from call queue pushback. > Always closing the connection degrades performance for all clients since a disconnected client will immediately reconnect on retry. Readers become overwhelmed servicing new connections and re-authentications from bad clients instead of servicing calls from good clients. The call queues run dry. > Exceptions originating in the readers should be able to indicate if the exception is an error or fatal so connections can remain open. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org