[
https://issues.apache.org/jira/browse/HDFS-17046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732984#comment-17732984
]
ASF GitHub Bot commented on HDFS-17046:
---------------------------------------
Hexiaoqiao commented on PR #5744:
URL: https://github.com/apache/hadoop/pull/5744#issuecomment-1592781982
@hfutatzhanghb Thanks to involve me here. I am not sure if you could solve
the issue as [HDFS-17046](https://issues.apache.org/jira/browse/HDFS-17046)
mentioned. I think we should choose one of the following ways,
a. forbid to move one path to home of Trash.
or
b. Emptier clean some directory at home of Trash which is not under
timestamp directory.
I prefer to solution b. Suggest to add config to enable it no matter which
solution we will choose. Thanks.
> Delete path directly when it 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
> Labels: pull-request-available
>
> 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]
