You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Thomas Graves (JIRA)" <ji...@apache.org> on 2012/09/06 18:59:07 UTC

[jira] [Created] (MAPREDUCE-4640) jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions

Thomas Graves created MAPREDUCE-4640:
----------------------------------------

             Summary: jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions
                 Key: MAPREDUCE-4640
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4640
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: jobhistoryserver
    Affects Versions: 0.23.3
            Reporter: Thomas Graves
            Assignee: Thomas Graves
            Priority: Critical


The JobHistoryEventHandler will create the done intermediate directory and its parents if it doesn't exist, but it doesn't properly set the parent directory permissions when the default umask is restrictive - 077.

Normally if you start the history server, it properly creates the directories with the right permissions  but if you don't start it before you run a job the parent directories get wrong permissions..

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

[jira] [Assigned] (MAPREDUCE-4640) jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions

Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Graves reassigned MAPREDUCE-4640:
----------------------------------------

    Assignee:     (was: Thomas Graves)
    
> jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4640
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4640
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>
> The JobHistoryEventHandler will create the done intermediate directory and its parents if it doesn't exist, but it doesn't properly set the parent directory permissions when the default umask is restrictive - 077.
> Normally if you start the history server, it properly creates the directories with the right permissions  but if you don't start it before you run a job the parent directories get wrong permissions..

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

[jira] [Commented] (MAPREDUCE-4640) jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions

Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449841#comment-13449841 ] 

Thomas Graves commented on MAPREDUCE-4640:
------------------------------------------

One correction - actually the history server will created them wrong also - it creates them with 770 and some of those parents could need 755.

I believe those directories are normally manually created by admins with proper permissions so not a blocker.
                
> jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4640
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4640
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Critical
>
> The JobHistoryEventHandler will create the done intermediate directory and its parents if it doesn't exist, but it doesn't properly set the parent directory permissions when the default umask is restrictive - 077.
> Normally if you start the history server, it properly creates the directories with the right permissions  but if you don't start it before you run a job the parent directories get wrong permissions..

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

[jira] [Updated] (MAPREDUCE-4640) jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions

Posted by "Thomas Graves (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-4640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Graves updated MAPREDUCE-4640:
-------------------------------------

    Priority: Major  (was: Critical)
    
> jobHistoryEventHandler doesn't fix done_intermediate parent directory permissions
> ---------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4640
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4640
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobhistoryserver
>    Affects Versions: 0.23.3
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>
> The JobHistoryEventHandler will create the done intermediate directory and its parents if it doesn't exist, but it doesn't properly set the parent directory permissions when the default umask is restrictive - 077.
> Normally if you start the history server, it properly creates the directories with the right permissions  but if you don't start it before you run a job the parent directories get wrong permissions..

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