hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1276) TaskTracker expiry interval is not configurable
Date Mon, 07 May 2007 20:17:15 GMT

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

Doug Cutting updated HADOOP-1276:
---------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this.  Thanks, Arun!

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


Mime
View raw message