hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1609) TaskTracker.localizeJob should not set permissions on job log directory recursively
Date Tue, 27 Apr 2010 08:18:32 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861303#action_12861303

Vinod K V commented on MAPREDUCE-1609:

The patch looks good. Only missed the javadoc for testTrackerReinit() and testTrackerRestart()
from the backport patch. If you include those and Hudson blesses the current patch, this one
will be good for commit.

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

View raw message