[jira] [Commented] (HDFS-7292) Improve error messages for checkOwner permission related failures

["Stephen Chu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184751#comment-14184751 ] 

Stephen Chu commented on HDFS-7292:
-----------------------------------

Hi, Harsh. I think this is the same as HDFS-6741. I submitted a patch there, and can further add more information about the inode in the message if you would like.

> 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
>            Priority: Trivial
>
> 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)