[jira] [Updated] (HDFS-17046) Delete directly when path can not be parsed in Trash.

["farmmamba (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDFS-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

farmmamba updated HDFS-17046:
-----------------------------
    Summary: Delete directly when path can not be parsed in Trash.  (was: Add metrics or delete directly when path can not parsed in Trash.)

> Delete directly when path can not be parsed in Trash.
> -----------------------------------------------------
>
>                 Key: HDFS-17046
>                 URL: https://issues.apache.org/jira/browse/HDFS-17046
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: farmmamba
>            Assignee: farmmamba
>            Priority: Major
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org