[HADOOP-15982] Support configurable trash location

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.0.0
• Component/s: fs
• Assignee: George Huang
• Reporter: George Huang
• Created: 06/Dec/18 01:30
• Updated: 14/Oct/19 15:38

Description

Currently some customer has users accounts that are functional ids (fid) to manage application and application data under the path /data/FID. These fid's also get a home directory under /user path. The user's home directories are limited with space quota 60 G. When these fids delete data, due to customer deletion policy they are placed in /user/<FID>/.Trash location and run over quota.

For now they are increasing quotas for these functional users, but considering growing applications they would like the .Trash location to be configurable or something like  /trash/{userid} that is owned by the user.

What should the configurable path look like to make this happen? For example, some thoughts may relate whether we want to configure it for per user or per cluster, etc.

Here is current behavior:

fs.TrashPolicyDefault: Moved: 'hdfs://ns1/user/hdfs/test/1.txt to trash at: hdfs://ns1/user/hdfs/.Trash/Current/user/hdfs/test/1.txt

for path under encryption zone:

fs.TrashPolicyDefault: Moved: 'hdfs://ns1/scale/2.txt' to trash at hdfs://ns1/scale/.Trash/hdfs/Current/scale/2.txt