[
https://issues.apache.org/jira/browse/HDFS-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498347#comment-17498347
]
Íñigo Goiri commented on HDFS-16487:
------------------------------------
At the end of the day, the idea of RBF is to unify all the federated
subclusters as a single filesystem.
For this reason, the mount points are shown as regular folders queried from the
RBF.
>From the description, I think the issue is that we can have a mountpoint that
>points to a location that is not present in the the destination cluster.
Can you elaborate with an example set of paths (both mount points and
subcluster) that would be misleading?
> RBF: getListing uses raw mount table points
> -------------------------------------------
>
> Key: HDFS-16487
> URL: https://issues.apache.org/jira/browse/HDFS-16487
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Fengnan Li
> Assignee: Aihua Xu
> Priority: Major
>
> In getListing, the result is a union of subclusters results and mount points.
> However these two are of different concepts and the latter one is something
> Router internal. It is very possible that the actual path doesn't exist in
> the dest HDFS yet.
> Can we choose a different strategy that check each children mount point and
> confirm there is the HDFS path in the dest cluster? If so, we can add it;
> otherwise we should skip this mount because it confuses clients. (Clients
> could directly create a subdir under a dangling mount point)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
