Amithsha created HDFS-15195:
-------------------------------
Summary: In place namenode fedaration
Key: HDFS-15195
URL: https://issues.apache.org/jira/browse/HDFS-15195
Project: Hadoop HDFS
Issue Type: New Feature
Reporter: Amithsha
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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
