[ https://issues.apache.org/jira/browse/HADOOP-18801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoqiao He resolved HADOOP-18801. ---------------------------------- Fix Version/s: 3.4.0 Hadoop Flags: Reviewed Resolution: Fixed > Delete path directly when it can not be parsed in trash > ------------------------------------------------------- > > Key: HADOOP-18801 > URL: https://issues.apache.org/jira/browse/HADOOP-18801 > Project: Hadoop Common > Issue Type: Improvement > Reporter: farmmamba > Assignee: farmmamba > Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > > 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. > > {code:java} > 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. > {code} > > -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org