hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-72) Move handling of Task debugging out of TaskTracker
Date Sat, 07 Jul 2012 16:13:34 GMT

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

Harsh J resolved MAPREDUCE-72.

    Resolution: Invalid

This is no longer needed to be done in the YARN and MR2 framework. Resolving as Invalid.
> Move handling of Task debugging out of TaskTracker
> --------------------------------------------------
>                 Key: MAPREDUCE-72
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-72
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Arun C Murthy
> Currently {{TaskTracker.TaskInProgress.taskFinished}} handles the responsibility of executing
the debug scripts for Map/Reduce tasks. Ideally we should keep this confined to TaskRunner
(which currently executes the actual tasks) or a separate pre/post processing classes.
> The current situation leads to bugs like HADOOP-3696.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message