hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1609) TaskTracker.lcoalizeJob should not set permissions on job log directory recursively
Date Mon, 22 Mar 2010 05:46:27 GMT

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

Amareshwari Sriramadasu updated MAPREDUCE-1609:
-----------------------------------------------

    Attachment: patch-1609.txt

Patch for trunk.
Patch incorporates MAPREDUCE-1595 as part of this fix, because the added testcase hits MAPREDUCE-1595
first and then this issue.

> TaskTracker.lcoalizeJob 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.lcoalizeJob 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 message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message