[
https://issues.apache.org/jira/browse/MAPREDUCE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798624#action_12798624
]
Jothi Padmanabhan commented on MAPREDUCE-1316:
----------------------------------------------
This looks good. I have a few minor comments w.r.t the test case:
# Should we put a limit on the number of times that we loop while waiting for
the TT to join so that we return back in reasonable time in case of some errors?
# Can we verify, just in case, that there are no Task status associated with
the TIP in question?
# {{// check that the first map to be scheduled}} - This comment needs fixing
# I am just wondering if it is better that we let the map complete and let
reducer be pending when we kill the job -- just to test the case where some
tips are done and some not?
> JobTracker holds stale references to retired jobs via unreported tasks
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-1316
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1316
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Attachments: mapreduce-1316-v1.11.patch, mapreduce-1316-v1.7.patch
>
>
> JobTracker fails to remove _unreported_ tasks' mapping from _taskToTIPMap_ if
> the job finishes and retires. _Unreported tasks_ refers to tasks that were
> scheduled but the tasktracker did not report back with the task status. In
> such cases a stale reference is held to TaskInProgress (and thus
> JobInProgress) long after the job is gone leading to memory leak.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
