[HADOOP-18801] Delete path directly when it can not be parsed in trash

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.0
• Fix Version/s: 3.4.0
• Component/s: common
• Labels: pull-request-available
• Target Version/s: 3.4.0
• Hadoop Flags: Reviewed
• Assignee: farmmamba
• Reporter: farmmamba
• Created: 13/Jun/23 07:35
• Updated: 27/Jan/24 08:19
• Resolved: 16/Jul/23 04:21

Description

If we move path to trash dir directly rather than use delete API or rm command, when 

invoke deleteCheckpoint method, it will catch ParseException and ignore deleting the path. It will never be deleted, so we should do something to prevent or monitor it.

Some logs are listed below.

 

WARN org.apache.hadoop.fs.TrashPolicyDefault: Unexpected item in trash: /user/de_eight/.Trash/college_geek_job_recall_als_modelres_5_2_6.del. Ignoring.

WARN org.apache.hadoop.fs.TrashPolicyDefault: Unexpected item in trash: /user/de_eight/.Trash/college_geek_addf_vector. Ignoring.
 

 

 

Issue Links

• links to: GitHub Pull Request #5744