Details
-
Improvement
-
Status: Resolved
-
Trivial
-
Resolution: Duplicate
-
2.2.0
-
None
-
None
Description
If a bad file create request fails, you get a juicy error self-describing the reason almost:
Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied: user=root, access=WRITE, inode="/":hdfs:supergroup:drwxr-xr-x
However, if a setPermission fails, one only gets a vague:
Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): Permission denied
It would be nicer if all forms of permission failures logged the accessed inode and current ownership and permissions in the same way.
Attachments
Attachments
Issue Links
- duplicates
-
HDFS-6741 Improve permission denied message when FSPermissionChecker#checkOwner fails
- Closed