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-4633) history server doesn't set permissions on all subdirs
Date Fri, 07 Sep 2012 14:02:15 GMT

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

Hudson commented on MAPREDUCE-4633:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #1189 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1189/])
    MAPREDUCE-4633. history server doesn't set permissions on all subdirs (tgraves via bobby)
(Revision 1381614)

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

                
> history server doesn't set permissions on all subdirs 
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-4633
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4633
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    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-4633.patch
>
>
> The job history server creates a bunch of subdirectories under the "done" directory.
 They are like 2012/09/03/000000.  It only sets the permissions on the last one, ie 000000
to 770.    So the 2012/09/03 aren't explicitly set so if the umask is more restrictive, they
won't be set as it expects.

--
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