hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4612) job summary file permissions not set when its created
Date Sat, 01 Sep 2012 14:02:08 GMT

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

Hudson commented on MAPREDUCE-4612:

Integrated in Hadoop-Mapreduce-trunk #1183 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1183/])
    MAPREDUCE-4612. job summary file permissions not set when its created (tgraves via bobby)
(Revision 1379584)

     Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1379584
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/jobhistory/JobHistoryEventHandler.java

> 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
>             Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>         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

View raw message