[
https://issues.apache.org/jira/browse/HDFS-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732050#comment-17732050
]
farmmamba commented on HDFS-17046:
----------------------------------
[~hexiaoqiao] Yes, sir. There will leave some directories in Trash home which
will not be clean by Empiter. It can be reproduced easily.
Just execute command like below and wait for next trash cleaning.
{code:java}
hdfs dfs -mv /path/to/your/file /user/hdfs/.Trash{code}
OK, sir. I will submit patch soonly, thanks so much for your comments.
> Add metrics or delete directly when path can not 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: [email protected]
For additional commands, e-mail: [email protected]
