[
https://issues.apache.org/jira/browse/HDFS-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099696#comment-14099696
]
Tsz Wo Nicholas Sze commented on HDFS-6801:
-------------------------------------------
For Jing's comment:
# Similar to Balancer, Mover is supposed to be run by admin and only one
instance is allowed. Users may request to set storage policy for their
directories but not run a separated Mover instance.
# You are right. We should dispatch pending moves as soon as possible.
> I think we can also handle the snapshot paths in a separate jira.
Sure, let's remove the snapshot related code here and handle snapshot files
separately.
> Archival Storage: Add a new data migration tool
> ------------------------------------------------
>
> Key: HDFS-6801
> URL: https://issues.apache.org/jira/browse/HDFS-6801
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer, namenode
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Attachments: h6801_20140813.patch, h6801_20140814.patch,
> h6801_20140814b.patch
>
>
> The tool is similar to Balancer. It periodic scans the blocks in HDFS and
> uses path and/or other meta data (e.g. mtime) to determine if a block should
> be cooled down (i.e. hot => warm, or warm => cold) or warmed up (i.e. cold =>
> warm, or warm => hot). In contrast to Balancer, the migration tool always
> move replicas to a different storage type. Similar to Balancer, the replicas
> are moved in a way that the number of racks the block does not decrease.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
