[HDFS-15181] Webhdfs getTrashRoot() causes internal AccessControlException

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Duplicate
• Component/s: webhdfs
• Target Version/s: 3.3.0, 3.1.4, 3.2.2, 2.10.1
• Assignee: Kihwal Lee
• Reporter: Kihwal Lee
• Created: 18/Feb/20 18:08
• Updated: 19/Feb/20 14:53
• Resolved: 19/Feb/20 14:53

Description

HDFS-10756 added the getTrashRoot() support for WebHdfs. However, it was done by creating a FileSystem instance in the namenode. This is unacceptable for many reasons and also the implementation is not correct. The current implementation only works when security is off. When security is on, the internal client received AccessControlException and does not work.

A similar bug was preset in HDFS-11156. Again, this is not merely a "performance bug". These don't work with security on. Fortunately HDFS-11156 was reverted and reworked. I've recently reverted it and ported the rework to branch-2.10.

Unless HDFS-10756 can be remedied quickly, it needs to be reverted.

Issue Links

• is broken by: HDFS-10756 Expose getTrashRoot to HTTPFS and WebHDFS
• is duplicated by: HDFS-15052 WebHDFS getTrashRoot leads to OOM due to FileSystem object creation
• is related to: HDFS-15052 WebHDFS getTrashRoot leads to OOM due to FileSystem object creation