[
https://issues.apache.org/jira/browse/HDFS-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603933#comment-17603933
]
ZanderXu commented on HDFS-8789:
--------------------------------
We plan to use the upgrade domain in our prod environment, so this tool will be
necessary for us before deploying the upgrade domain.
After looking into the upgradeDomain(UD) and this migrator tool, maybe there
are some improvements we can do:
* After deploying the UD, namenode should not try to migrate the old blocks
after become the active during processMisReplicatesAsync. We should migrate the
old blocks by this migrator tool.
* Maybe we can integrate this migrator to mover. And we can just simply add
one new processFile method in mover to achieve the goals that migrating the
blocks that didn't satisfy the block placement policy.
[~weichiu] [~sodonnell] [~ctrezzo] Do you have plans to push this PR forward?
If have, I have done some works and interested in carrying it forward.
> 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
