hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hans Uhlig (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-4220) Augment AccessControlException to include both affected inode and attempted operation
Date Wed, 21 Nov 2012 03:26:58 GMT
Hans Uhlig created HDFS-4220:
--------------------------------

             Summary: Augment AccessControlException to include both affected inode and attempted
operation
                 Key: HDFS-4220
                 URL: https://issues.apache.org/jira/browse/HDFS-4220
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: hdfs client, name-node
    Affects Versions: 2.0.2-alpha
            Reporter: Hans Uhlig
            Priority: Minor


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.



--
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

Mime
View raw message