[
https://issues.apache.org/jira/browse/HDFS-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190883#comment-17190883
]
Ayush Saxena commented on HDFS-15554:
-------------------------------------
Thanx [~fengnanli] for the report, I just had a quick look on the
description(couldn't check the code), and seems like you want to avoid adding a
mount entry if the destination directory doesn't exist, so as to avoid FNF's
later, right?
Will HDFS-13506 help? It aims to create the directory if it doesn't exist in
the actual NS. Blocking addition of mount entries if destination directory
isn't there would be an incompatible change as well. An admin might add a mount
entry first and then create the destination directories, that is something. I
am pretty sure, if we throw an exception a lot of test scripts are gonna break.
> RBF: force router check file existence in destinations before adding/updating
> mount points
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-15554
> URL: https://issues.apache.org/jira/browse/HDFS-15554
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Fengnan Li
> Assignee: Fengnan Li
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Adding/Updating mount points right now is only a router action without
> validation in the downstream namenodes for the destination files/directories.
> In practice we have set up the dangling mount points and when clients call
> listStatus they would get the file returned, but then if they try to access
> the file FileNotFoundException would be thrown out.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
