hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4612) job summary file permissions not set when its created
Date Fri, 31 Aug 2012 20:14:07 GMT

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

Robert Joseph Evans commented on MAPREDUCE-4612:
------------------------------------------------

The patch looks good to me.  +1 assuming Jenkins comes back OK barring the missing test.
                
> job summary file permissions not set when its created
> -----------------------------------------------------
>
>                 Key: MAPREDUCE-4612
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4612
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.23.3, 3.0.0, 2.2.0-alpha
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Critical
>         Attachments: MAPREDUCE-4612.patch
>
>
> The job summary file permissions are not set when its written out by to the done intermediate
directory. The conf and jhist files are both set properly but the summary file doesn't follow
the same path.  
> This can cause the summary file to not be copied to the done directory if the default
umask is set to be restrictive (like 600) and the mapred user can't read it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message