Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <18121884.1178266816419.JavaMail.jira@brutus>
Date: Fri, 4 May 2007 01:20:16 -0700 (PDT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Assigned: (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


     [ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy reassigned HADOOP-1276:
-------------------------------------

    Assignee: Arun C Murthy

> 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
>
>
> 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.