You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Raj Vishwanathan (JIRA)" <ji...@apache.org> on 2011/02/17 15:42:48 UTC
[jira] Commented: (MAPREDUCE-2327) MapTask doesn't need to put
username information in SpillRecord
[ https://issues.apache.org/jira/browse/MAPREDUCE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995830#comment-12995830 ]
Raj Vishwanathan commented on MAPREDUCE-2327:
---------------------------------------------
Todd
This looks like the bug I hit. Can I work around it by running the job as the user mapred? From the bug report, that should work.
Raj
> 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: 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