[
https://issues.apache.org/jira/browse/HADOOP-18998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791966#comment-17791966
]
ASF GitHub Bot commented on HADOOP-18998:
-----------------------------------------
slfan1989 commented on PR #6312:
URL: https://github.com/apache/hadoop/pull/6312#issuecomment-1835751042
@LiuGuH This seems to be an HDFS JIRA, not a HADOOP JIRA. Why do we need to
configure `fs.trash.checkpoint.interval` set to 10min, generally this should be
at least 1 day or more.
> [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]
