You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2014/10/27 08:36:34 UTC
[jira] [Assigned] (HDFS-7292) Improve error messages for checkOwner
permission related failures
[ https://issues.apache.org/jira/browse/HDFS-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J reassigned HDFS-7292:
-----------------------------
Assignee: Harsh J
> Improve error messages for checkOwner permission related failures
> -----------------------------------------------------------------
>
> Key: HDFS-7292
> URL: https://issues.apache.org/jira/browse/HDFS-7292
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.2.0
> Reporter: Harsh J
> Assignee: Harsh J
> Priority: Trivial
> Attachments: HDFS-7292.patch
>
>
> If a bad file create request fails, you get a juicy error self-describing the reason almost:
> {code}Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied: user=root, access=WRITE, inode="/":hdfs:supergroup:drwxr-xr-x{code}
> However, if a setPermission fails, one only gets a vague:
> {code}Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied{code}
> It would be nicer if all forms of permission failures logged the accessed inode and current ownership and permissions in the same way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)