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 AF225106AF for ; Tue, 26 Nov 2013 05:06:39 +0000 (UTC) Received: (qmail 66392 invoked by uid 500); 26 Nov 2013 05:06:38 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 66204 invoked by uid 500); 26 Nov 2013 05:06:36 -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 66187 invoked by uid 99); 26 Nov 2013 05:06:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 05:06:35 +0000 Date: Tue, 26 Nov 2013 05:06:35 +0000 (UTC) From: "Hadoop QA (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=13832320#comment-13832320 ] Hadoop QA commented on HADOOP-10127: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12615768/hadoop-10127-1.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3313//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3313//console This message is automatically generated. > 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, the client attempts to connect to the server every 1 second. It would be nice to make this configurable so that the client can connect more/less frequently. Changing the number of retries alone is not granular enough. -- This message was sent by Atlassian JIRA (v6.1#6144)