[
https://issues.apache.org/jira/browse/HDFS-15554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190948#comment-17190948
]
Ayush Saxena commented on HDFS-15554:
-------------------------------------
Thanx [~fengnanli] for sharing the use case. I just saw there are bunch of test
failures as well. so, that even gives me a feel, and TBH I don't think the
current workflow is anyway 'wrong', It is just that it doesn't satisfy your use
case. I am in general no favour of going ahead with such an incompatible way.
The best I can suggest is, back this with a configuration, turn that off by
default, and you guys can enable it, as per need, This may even prevent you
from fixing the tests as well.
> 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]
