[
https://issues.apache.org/jira/browse/HDFS-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603955#comment-17603955
]
ZanderXu commented on HDFS-8789:
--------------------------------
After quickly looking HDFS-14053, it can migrate the old blocks to satisfy the
new block placement policy. But if all the old blocks are migrated by namenode,
it will affect the processing performance of Namenode even if we can limit the
speed of migration. It would be nice to have a peripheral migration tool that
can migrate old blocks automatically, efficiently, and with minimal impact.
Beside this migrator, do you have disabled migrating the blocks after namenode
become active? [~sodonnell] . Because after namenode become active, it will
processMisReplicatedBlocks.
> Block Placement policy migrator
> -------------------------------
>
> Key: HDFS-8789
> URL: https://issues.apache.org/jira/browse/HDFS-8789
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Chris Trezzo
> Assignee: Chris Trezzo
> Priority: Major
> Attachments: HDFS-8789-trunk-STRAWMAN-v1.patch
>
>
> As we start to add new block placement policies to HDFS, it will be necessary
> to have a robust tool that can migrate HDFS blocks between placement
> policies. This jira is for the design and implementation of that tool.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
