[
https://issues.apache.org/jira/browse/HDFS-15195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17047582#comment-17047582
]
Amithsha edited comment on HDFS-15195 at 3/2/20 6:51 AM:
---------------------------------------------------------
Yes https://issues.apache.org/jira/browse/HDFS-7702 this is my requirement
Dynamic Namenode federation. But no further update on the same.
was (Author: amithsha):
Yes https://issues.apache.org/jira/browse/HDFS-7702 this is my requirement
Dynamic Namenode federation. But further update on the same.
> In place namenode federation
> ----------------------------
>
> Key: HDFS-15195
> URL: https://issues.apache.org/jira/browse/HDFS-15195
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Amithsha
> Priority: Major
>
> In the current scenario federating the existing data is not possible. This
> impacts the implementation of HDFS federation on the production cluster with
> more than PB of data. Because we need to copy the data from the old set of
> namenodes to the new set of namenodes. From the data node directory structure
> its clear that if we move the blocks of particular data from namenode_set_1
> dir (dfs/data/current/BP-xxx) to namenode_set_2 dir (dfs/data/current/BP-yyy)
> will solve the issue. Why can’t we make this us a new future where it will
> ask for dir to get federated and stop the write process until move completes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
