[ 
https://issues.apache.org/jira/browse/HDFS-15087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013422#comment-17013422
 ] 

Brahma Reddy Battula commented on HDFS-15087:
---------------------------------------------

[~LiJinglun] . Gone through the design document,Nice Feature and Neatly 
docuemented. (y) 

 
 # Scheduler will have ablitiy to identify which NS is full and automatically 
schedule the job..? May be each NS can configure the threshhold..?
 # Scheduler can be enchanced based RPC load/usage ( balance the RPC load 
also)..?
 # How the consistency is ensured if you wn't use snapshot like [~linyiqun]  
and [~goiri]  mentioned..? After "*saveTree"* step, before creating the mount 
table(Or blockwrites will be there till job is success, but this might delay 
other applications as you make tree as immutable?) .how the delta will be 
processed..?  ( i didn't seen, making mount table readonly)..Bytheway editlog 
idea looks good here.
 # Mount table properties(or attributes) also preserved..? 
 # saveTree() and GraftTree() are idempotent..? On Namenode failover, will 
these be re-executed if it's connected to newly active namenode.

Please do correct me if I am not in same page with you guys.

Bytheway I am planning for 3.3.0 release by March mid, it will be good if we 
finish before that, so that this can be included in 3.3 Release.

> RBF: Balance/Rename across federation namespaces
> ------------------------------------------------
>
>                 Key: HDFS-15087
>                 URL: https://issues.apache.org/jira/browse/HDFS-15087
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Jinglun
>            Priority: Major
>         Attachments: HDFS-15087.initial.patch, HFR_Rename Across Federation 
> Namespaces.pdf
>
>
> The Xiaomi storage team has developed a new feature called HFR(HDFS 
> Federation Rename) that enables us to do balance/rename across federation 
> namespaces. The idea is to first move the meta to the dst NameNode and then 
> link all the replicas. It has been working in our largest production cluster 
> for 2 months. We use it to balance the namespaces. It turns out HFR is fast 
> and flexible. The detail could be found in the design doc. 
> Looking forward to a lively discussion.



--
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

Reply via email to