[
https://issues.apache.org/jira/browse/MAPREDUCE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod K V updated MAPREDUCE-1609:
---------------------------------
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Release Note: Fixed TaskTracker so that it does not set permissions on
job-log directory recursively. This fix both improves the performance of job
localization as well as avoids a bug related to launching of task-cleanup
attempts after TaskTracker's restart.
Resolution: Fixed
I just committed this. Thanks Amareshwari!
> TaskTracker.localizeJob should not set permissions on job log directory
> recursively
> -----------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1609
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1609
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.22.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1609-20-1.patch, patch-1609-1.txt,
> patch-1609.txt
>
>
> Currently TaskTracker.localizeJob sets permissions (570 with
> LinuxTaskController) on job log directory recursively. When the tracker
> restarts/reinits, if there are new tasks for the job, localizeJob would find
> attempt log directories for the earlier tasks. If the job has many tasks, it
> would spend significant time in chmod'ing.
> Also, if a cleanup attempt is launched after the restart/reinit, we would hit
> MAPREDUCE-1607.
> This problem is missed by the patch for MAPREDUCE-927. The above problem
> never existed before MAPREDUCE:927.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
