[
https://issues.apache.org/jira/browse/HDFS-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243793#comment-17243793
]
Ayush Saxena commented on HDFS-14431:
-------------------------------------
Thanx [~LiJinglun] for the response, Sorry, I missed the notification
Yes the client timeout shall be a problem, distCp is gonna take time. But just
for the sake of knowledge, if the client has timeout sorted, or he isn't
renaming too big files, Can we try implementing just a basic distCp stuff, May
be mark it as optional and turned off by default.
Regarding failover, I am not sure that is something needed, If the Router
crashes, the client call shall also fail, The client would shoot it's call to
another Router, in a similar manor if one Namenode crashes, Yahh, there would
be performance issues, but that we can consider, once at least a basic rename
framework works. :)
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
