[
https://issues.apache.org/jira/browse/HDFS-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849784#comment-16849784
]
xuzq commented on HDFS-14431:
-----------------------------
Thanx [~elgoiri] for the update.
I came across a scenario when rename src to dest but I don't have good solution
to fix it , do you have any idea?
Like this:
* src mount to ns1 and ns2, and both in ns1 and ns2.
* dst mount to ns2 and ns3, and both in ns2 and ns3.
[^HDFS-14431-HDFS-13891.007.patch] will rename src to dst in ns2, and may be
delete dst data in ns3 if it support overwrite.
But ns1 still have the src file or directory which is renamed successfully.
When user get listing the src, there are still have some datas which got from
from ns1, it may be stupid.
Do you have some ideas to fix it? cc [~ayushtkn]
> RBF: Rename with multiple subclusters should fail if no eligible locations
> --------------------------------------------------------------------------
>
> Key: HDFS-14431
> URL: https://issues.apache.org/jira/browse/HDFS-14431
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: Íñigo Goiri
> Priority: Major
> Attachments: HDFS-14431-HDFS-13891.001.patch,
> HDFS-14431-HDFS-13891.002.patch, HDFS-14431-HDFS-13891.003.patch,
> HDFS-14431-HDFS-13891.004.patch, HDFS-14431-HDFS-13891.005.patch,
> HDFS-14431-HDFS-13891.006.patch, HDFS-14431-HDFS-13891.007.patch
>
>
> Currently, the rename will fail with FileNotFoundException which is not clear
> to the user.
> The operation should fail stating the reason is that there are no eligible
> destinations.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
