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 "Jeff Hammerbacher (Updated) (JIRA)" <ji...@apache.org> on 2012/04/01 07:54:57 UTC

[jira] [Updated] (MAPREDUCE-4070) JobHistoryServer creates /tmp directory with restrictive permissions if the directory doesn't already exist.

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

Jeff Hammerbacher updated MAPREDUCE-4070:
-----------------------------------------

    Summary: JobHistoryServer creates /tmp directory with restrictive permissions if the directory doesn't already exist.  (was: JonHistoryServer creates /tmp directory with restrictive permissions if the directory doesn't already exist.)
    
> JobHistoryServer creates /tmp directory with restrictive permissions if the directory doesn't already exist.
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4070
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4070
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Ahmed Radwan
>            Assignee: Ahmed Radwan
>             Fix For: 0.23.2
>
>         Attachments: MAPREDUCE-4070.patch
>
>
> Starting up the MapReduce JobhHistoryServer service after a clean install appears to automatically create the /tmp directory on HDFS. However, it is created with 750 permission.
> Attempting to run MR jobs by other users results in the following permissions exception:
> {code}
> org.apache.hadoop.security.AccessControlException: Permission denied: user=cloudera, access=EXECUTE, inode="/tmp":yarn:supergroup:drwxr-x---
> at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:205)
> ..
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira