hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-7033) Map outputs implicitly rely on permissive umask for shuffle
Date Thu, 01 Feb 2018 14:24:00 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-7033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Eric Payne updated MAPREDUCE-7033:
       Resolution: Fixed
    Fix Version/s: 3.0.1
           Status: Resolved  (was: Patch Available)

> 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
>             Fix For: 3.1.0, 3.0.1
>         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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message