You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2018/01/31 21:03:00 UTC
[jira] [Commented] (TEZ-3894) Tez intermediate outputs implicitly
rely on permissive umask for shuffle
[ https://issues.apache.org/jira/browse/TEZ-3894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347600#comment-16347600 ]
Jason Lowe commented on TEZ-3894:
---------------------------------
This is the Tez equivalent of MAPREDUCE-7033. This will become more of an issue with Hadoop 3.x since HADOOP-11347 fixed a bug in the local filesystem to have it honor the configured fs.permission.umask-mode property where it was ignored in 2.x and implicitly relied on the UNIX umask.
> 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
>
> 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)