[
https://issues.apache.org/jira/browse/HADOOP-18998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791970#comment-17791970
]
ASF GitHub Bot commented on HADOOP-18998:
-----------------------------------------
LiuGuH commented on PR #6312:
URL: https://github.com/apache/hadoop/pull/6312#issuecomment-1835765866
> @LiuGuH This seems to be an HDFS JIRA, not a HADOOP JIRA.
Yes, it is an HDFS JIRA, thanks. I will create a new one JIRA. Thanks
> Why do we need to configure `fs.trash.checkpoint.interval` set to 10min,
generally this should be at least 1 day or more.
It can be 1 day or more, and if 1 day later or more, the user ls trash root
, it will not see /user/$USER/.Trash/timestamp dir if the dir is in ns1.
In additional, `fs.trash.checkpoint.interval` will be set to a small value
in order to avoid delelte a lot of blocks with write lock competition in
FSNameSystem.
> [RBF] Make listStatus user root trash dir will return all subclusters trash
> subdirs if user has any mount points in nameservice.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-18998
> URL: https://issues.apache.org/jira/browse/HADOOP-18998
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: liuguanghua
> Priority: Minor
> Labels: pull-request-available
>
> Same scenario as HDFS-17263
> If user trash config fs.trash.checkpoint.interval set to 10min in namenodes,
> the trash root dir /user/$USER/.Trash/Current will be very 10 min renamed to
> /user/$USER/.Trash/timestamp .
>
> When user ls /user/$USER/.Trash, it should be return blow:
> /user/$USER/.Trash/Current
> /user/$USER/.Trash/timestamp (This is invisible now)
>
> So we should make that user ls trash root dir can see all trash subdirs in
> all nameservices which user has any mountpoint in nameservice.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
