Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 75383 invoked from network); 4 May 2007 08:58:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 May 2007 08:58:38 -0000 Received: (qmail 6774 invoked by uid 500); 4 May 2007 08:58:43 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 6755 invoked by uid 500); 4 May 2007 08:58:43 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 6746 invoked by uid 99); 4 May 2007 08:58:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2007 01:58:43 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2007 01:58:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 9C154714049 for ; Fri, 4 May 2007 01:58:15 -0700 (PDT) Message-ID: <21477973.1178269095629.JavaMail.jira@brutus> Date: Fri, 4 May 2007 01:58:15 -0700 (PDT) From: "Arun C Murthy (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-1276) TaskTracker expiry interval is not configurable In-Reply-To: <23340942.1177047555276.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493624 ] Arun C Murthy commented on HADOOP-1276: --------------------------------------- Here is a straight-forward patch... Personally I find this feature quite useful, especially when dealing with issues relating to lost trackers... I'm not very sure about the original constraints which led to this being hard-coded and would acquiesce to the same. > TaskTracker expiry interval is not configurable > ----------------------------------------------- > > Key: HADOOP-1276 > URL: https://issues.apache.org/jira/browse/HADOOP-1276 > Project: Hadoop > Issue Type: Improvement > Components: mapred > Environment: all > Reporter: Alejandro Abdelnur > Assigned To: Arun C Murthy > Fix For: 0.13.0 > > Attachments: HADOOP-1276_20070504_1.patch > > > The tasktracker expiry interval is hardcoded to 10 mins with the MRConstants.TASKTRACKER_EXPIRY_INTERVAL constant. > For small clusters, running small jobs, this interval is too high. > Making it configurable it would require: > * Introducing a 'tasktracker.expiry.interval' property with default value of 10 mins. > * Load the property in the JobTracker > * Change the 5 usages of the constant by a property in the JobTracker > * Remove the constant from MRConstants > * add default value to the hadoop-default.xml file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.