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

Kuhu Shukla commented on TEZ-3894:
----------------------------------

Precommit Output:
{noformat}
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12909299/TEZ-3894.001.patch
  against master revision 96c988c.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/2725//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2725//console
{noformat}

> Tez intermediate outputs implicitly rely on permissive umask for shuffle
> ------------------------------------------------------------------------
>
>                 Key: TEZ-3894
>                 URL: https://issues.apache.org/jira/browse/TEZ-3894
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Major
>         Attachments: TEZ-3894.001.patch
>
>
> Tez does not explicitly set the permissions of intermediate output files for 
> shuffle. In a secure cluster the shuffle service is running as a different 
> user than the task, so the output files require group readability in order to 
> serve up the data during the shuffle phase. If the umask is too restrictive 
> (e.g.: 077) then the 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)

Reply via email to