You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2007/05/04 10:20:16 UTC
[jira] Assigned: (HADOOP-1276) TaskTracker expiry interval is not
configurable
[ 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.