hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2327) MapTask doesn't need to put username information in SpillRecord
Date Thu, 28 Apr 2011 05:29:03 GMT

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

Todd Lipcon updated MAPREDUCE-2327:

    Attachment: mapreduce-2327.txt

Good point on the config name. Fixed.

As for whether this is actually a real bug -- now that HADOOP-7172 has gone in, you're right
that this won't cause a problem. But, as a matter of principle, we might as well put the right
expected owner in the data structure :)

> MapTask doesn't need to put username information in SpillRecord
> ---------------------------------------------------------------
>                 Key: MAPREDUCE-2327
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2327
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.22.0
>         Attachments: mapreduce-2327.txt, mapreduce-2327.txt, mr-2327.txt
> This is an amendment to MAPREDUCE-2096 that's found in Yahoo's 0.20.100 branch.
> This bug causes task failures in the following case:
> - Cluster is not set up with LinuxTaskController (ie not secured cluster)
> - Job submitter is not the same as the user running the TT
> - Map output is more than one spill's worth
> The issue is that UserGroupInformation's view of the current user is the job submitter,
but on disk the spill files will be owned by the TT user. SecureIO will then fail when constructing
the spill record.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message