Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 14 May 2011 04:10:47 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <577555482.12367.1305346247531.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <866822897.16484.1297734118147.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-2327) MapTask doesn't need to put
 username information in SpillRecord
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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

Sure, here's an updated patch that does that.

> 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