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 "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2007/04/20 07:39:15 UTC
[jira] Created: (HADOOP-1276) TaskTracker expiry interval is not
configurable
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
Priority: Minor
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.
[jira] Updated: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-1276:
----------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Commented: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494257 ]
Hadoop QA commented on HADOOP-1276:
-----------------------------------
Integrated in Hadoop-Nightly #82 (See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/82/)
> 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.
[jira] Updated: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-1276:
----------------------------------
Attachment: HADOOP-1276_20070504_1.patch
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 to 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.
[jira] Assigned: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated HADOOP-1276:
---------------------------------------
Priority: Major (was: Minor)
> 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
> 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.
[jira] Commented: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Arun C Murthy (JIRA)" <ji...@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.
[jira] Updated: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HADOOP-1276:
----------------------------------
Comment: was deleted
> 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.
[jira] Updated: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-1276) TaskTracker expiry interval is not
configurable
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493621 ]
Hadoop QA commented on HADOOP-1276:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12356754/HADOOP-1276_20070504_1.patch applied and successfully tested against trunk revision r534975.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/117/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/117/console
> 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.