Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 7364 invoked from network); 21 May 2009 05:18:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 May 2009 05:18:58 -0000 Received: (qmail 31738 invoked by uid 500); 21 May 2009 05:19:10 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 31678 invoked by uid 500); 21 May 2009 05:19:10 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 31668 invoked by uid 99); 21 May 2009 05:19:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 05:19:10 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 May 2009 05:19:06 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C327E234C004 for ; Wed, 20 May 2009 22:18:45 -0700 (PDT) Message-ID: <154837375.1242883125787.JavaMail.jira@brutus> Date: Wed, 20 May 2009 22:18:45 -0700 (PDT) From: "Amareshwari Sriramadasu (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-5784) The length of the heartbeat cycle should be configurable. In-Reply-To: <669094532.1241766705665.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711466#action_12711466 ] Amareshwari Sriramadasu commented on HADOOP-5784: ------------------------------------------------- Current heartbeat interval is set to {{clusterSize / 100}}, and minimum interval is capped at 3seconds. It assumes that JT can process 100 heartbeats in a second. See http://issues.apache.org/jira/browse/HADOOP-1900?focusedCommentId=12542530&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12542530 Now, if we make number of heartbeats that should arrive in a second configurable (with default value as 100) , heartbeat interval can be calculated as {code} heartbeatInterval = max((clusterSize / #heartbeats in a second), HEARTBEAT_INTERVAL_MIN) ; {code} Thoughts? > The length of the heartbeat cycle should be configurable. > --------------------------------------------------------- > > Key: HADOOP-5784 > URL: https://issues.apache.org/jira/browse/HADOOP-5784 > Project: Hadoop Core > Issue Type: Improvement > Components: mapred > Reporter: Owen O'Malley > > Currently, the hearbeat cycle is set to (# nodes / 100) in seconds. This can be too long for clusters that need to run low latency jobs. We should make the number of heartbeats that should arrive a second configurable. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.