[HDFS-4220] Augment AccessControlException to include both affected inode and attempted operation

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0.2-alpha
• Component/s: hdfs-client, namenode
• Labels: documentation
• Target Version/s: 2.0.2-alpha
• Assignee: Unassigned
• Reporter: Hans Uhlig
• Created: 21/Nov/12 03:26
• Updated: 20/May/13 19:15

Description

Currently when any application that uses hdfs runs and hits a permissions wall a message similar to the following is emitted.

FAILED: RuntimeException org.apache.hadoop.security.AccessControlException: Permission denied: user=huhlig, access=WRITE, inode="/":hdfs:hadoop:drwxr-xr-x

This provides a bit of information including who, did what and where but not what I tried to do. This makes debugging naughty or misconfigured applications difficult to debug.

A preferable addition to this would follow inode

FAILED: RuntimeException org.apache.hadoop.security.AccessControlException: Permission denied: user=huhlig, access=WRITE, inode="/":hdfs:hadoop:drwxr-xr-x, operation=mkdir:"/new/path/to/make"

This would allow for easier tracing of applications like hive where they may hit odd file system spaces.