[
https://issues.apache.org/jira/browse/HDFS-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687641#comment-13687641
]
Fengdong Yu commented on HDFS-4918:
-----------------------------------
bq.The issue (I don't think its snapshot related either) is that the NN RPC
call of setPermission does not check the state of isPermissionsEnabled. The
user thread for this report is http://search-hadoop.com/m/r91Yo1soPIp.
I enabled permission in my test cluster. because "dfs.permissions.enabled" is
true by default. then I cannot submit MR,
so I don't think NN RPC call doesn't check "dfs.permissions.enabled". and I
checked code again. It does check.
after submit MR, found on the job tracker.
{code}
Failure Info: Job initialization failed:
org.apache.hadoop.security.AccessControlException: Permission denied:
user=hadoop, access=EXECUTE,
inode="/data/hadoop/data/mapred/system":hadoop:supergroup:drwx------ at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:238)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkTraverse(FSPermissionChecker.java:191)
at
org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:154)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:4848)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:4830)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkAncestorAccess(FSNamesystem.java:4804)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInternal(FSNamesystem.java:1927)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:1870)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:1827)
at
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:459)
at
{code}
> HDFS permission check is incorrect
> ----------------------------------
>
> Key: HDFS-4918
> URL: https://issues.apache.org/jira/browse/HDFS-4918
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client, namenode
> Affects Versions: 2.0.0-alpha
> Reporter: Fengdong Yu
>
> HDFS permisson check is incorrect, even if dfs.permissions is set false. it
> does look like this was caused by snap shot.
--
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
