[
https://issues.apache.org/jira/browse/HDFS-14591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena reopened HDFS-14591:
---------------------------------
Reopened and closing again as duplicate rather than fixed.
> NameNode should move the replicas to the correct storages after the storage
> policy is changed.
> ----------------------------------------------------------------------------------------------
>
> Key: HDFS-14591
> URL: https://issues.apache.org/jira/browse/HDFS-14591
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
>
> Our Xiaomi HDFS has a cluster storaging both HOT and COLD data. We have a
> backgroud process searching all the files to find those that are not accessed
> for a period of time. Then we set them to COLD and start a mover to move the
> replicas. After moving, all the replicas are consistent with the storage
> policy.
> It's a natural idea to let the NameNode handle the move.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
