[
https://issues.apache.org/jira/browse/MAPREDUCE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated MAPREDUCE-2327:
---------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I've just committed this. Thanks, Todd!
> 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,
> 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