You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "zhengchenyu (Jira)" <ji...@apache.org> on 2021/02/22 08:07:00 UTC
[jira] [Commented] (HDFS-14343) RBF: Fix renaming folders spread
across multiple subclusters
[ https://issues.apache.org/jira/browse/HDFS-14343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288235#comment-17288235 ]
zhengchenyu commented on HDFS-14343:
------------------------------------
[~ayushtkn] Maybe I think we should discuss in another issue HDFS-15750.
I known there is no problem if all hdfs client visit namenode through router. But I think there are some situation that visit namnode without router.
For example, we migrating data from one nameservice to another nameservice in background, and two nameservie are managed by same router, we migration data to lower the pressure of source namenode.
> RBF: Fix renaming folders spread across multiple subclusters
> ------------------------------------------------------------
>
> Key: HDFS-14343
> URL: https://issues.apache.org/jira/browse/HDFS-14343
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Íñigo Goiri
> Assignee: Ayush Saxena
> Priority: Major
> Fix For: 3.3.0, HDFS-13891
>
> Attachments: HDFS-14343-HDFS-13891-01.patch, HDFS-14343-HDFS-13891-02.patch, HDFS-14343-HDFS-13891-03.patch, HDFS-14343-HDFS-13891-04.patch, HDFS-14343-HDFS-13891-05.patch
>
>
> The {{RouterClientProtocol#rename()}} function assumes that we are renaming files and only renames one of them (i.e., {{invokeSequential()}}). In the case of folders which are in all subclusters (e.g., HASH_ALL) we should rename all locations (i.e., {{invokeAll()}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org