Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5DC81106FE for ; Fri, 29 Nov 2013 06:55:46 +0000 (UTC) Received: (qmail 5540 invoked by uid 500); 29 Nov 2013 06:55:45 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 5488 invoked by uid 500); 29 Nov 2013 06:55:39 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 5472 invoked by uid 99); 29 Nov 2013 06:55:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Nov 2013 06:55:36 +0000 Date: Fri, 29 Nov 2013 06:55:36 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-10127) Add ipc.client.connect.retry.interval to control the frequency of connection retries 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/HADOOP-10127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13835212#comment-13835212 ] Karthik Kambatla commented on HADOOP-10127: ------------------------------------------- [~sandyr] and [~stevel], thanks for the discussion. Agree with you both on how to handle this. I propose the following: # Add ipc.client.connect.retry.interval in this JIRA, so the knob is available to be played with in YARN. # YARN-1028 would implement ConfiguredFailoverProxyProvider with the not-so-nice 10 second delay to failover for all entities connecting to the RM. # YARN-1460 to define yarn-specific ipc-client configs that the clients use, and add an exponential backoff and jitter at least for NM -> RM. With that plan, what do you think of the current patch? > Add ipc.client.connect.retry.interval to control the frequency of connection retries > ------------------------------------------------------------------------------------ > > Key: HADOOP-10127 > URL: https://issues.apache.org/jira/browse/HADOOP-10127 > Project: Hadoop Common > Issue Type: Bug > Components: ipc > Affects Versions: 2.2.0 > Reporter: Karthik Kambatla > Assignee: Karthik Kambatla > Attachments: hadoop-10127-1.patch > > > Currently, {{ipc.Client}} client attempts to connect to the server every 1 second. It would be nice to make this configurable to be able to connect more/less frequently. Changing the number of retries alone is not granular enough. -- This message was sent by Atlassian JIRA (v6.1#6144)