[
https://issues.apache.org/jira/browse/MAPREDUCE-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239019#comment-13239019
]
Hadoop QA commented on MAPREDUCE-4070:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12520021/MAPREDUCE-4070.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2106//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2106//console
This message is automatically generated.
> JonHistoryServer 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
