[ 
https://issues.apache.org/jira/browse/MAPREDUCE-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347689#comment-16347689
 ] 

Hudson commented on MAPREDUCE-7033:
-----------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13594 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/13594/])
MAPREDUCE-7033: Map outputs implicitly rely on permissive umask for (epayne: 
rev 5a725bb886eb0b9182840c4a91466c361ecc11e0)
* (edit) 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
* (add) 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/test/java/org/apache/hadoop/mapred/TestMapTask.java


> Map outputs implicitly rely on permissive umask for shuffle
> -----------------------------------------------------------
>
>                 Key: MAPREDUCE-7033
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7033
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Critical
>         Attachments: MAPREDUCE-7033.001.patch, MAPREDUCE-7033.002.patch
>
>
> Map tasks do not explicitly set the permissions of their output files for 
> shuffle.  In a secure cluster the shuffle service is running as a different 
> user than the map task, so the output files require group readability in 
> order to serve up the data during the shuffle phase.  If the user's UNIX 
> umask is too restrictive (e.g.: 077) then the map task's file.out and 
> file.out.index permissions can be too restrictive to allow the shuffle 
> handler to access them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to