-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDFS-17269. RBF: Listing trash directory should return subdirs from all subclusters. #6312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… trash subdirs if user has any mount points in nameservice.
|
@LiuGuH This seems to be an HDFS JIRA, not a HADOOP JIRA. Why do we need to configure From a practical need perspective, do we need to do this? Displaying the trash of the default namespace is in line with expectations. For example, if we have many namespaces, displaying the trash of all namespaces does not seem to be a good way. |
Yes, it is an HDFS JIRA, thanks. I will create a new one JIRA.
It can be 1 day or more, and then 1 day later or more time passed, the user ls trash root , it will not see /user/$USER/.Trash/timestamp dir if the dir is in ns1. |
|
🎊 +1 overall
This message was automatically generated. |
|
@LiuGuH Would it be more chaotic to display the trash directories of all clusters at once? Should we allow users to choose whether to display the trash directories of all subgroups through more configuration options, instead of enforcing such behavior |
...-hdfs-rbf/src/test/java/org/apache/hadoop/hdfs/server/federation/router/TestRouterTrash.java
Show resolved
Hide resolved
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
Thanks for review. This will display the trash directories of all clusters at once if the clusters have any moint point. Add this in getDestinationForPath() will be minimum change. And it should not use more configuration to control this : For client view , it is better to display all trash from all clusters that have any moint point. @zhtttylz |
I agree with @zhtttylz idea. For a cluster with 7-8 NS, it is not friendly. |
But for user view, it does not care how many nameservices it has. And only the nameservices that have mount point will return. Even if a cluster with 7-8 NS, the trash should return all trash that the user really has trash dir in that nameservices. |
|
🎊 +1 overall
This message was automatically generated. |
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
Description of PR
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.