You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Vinayakumar B (JIRA)" <ji...@apache.org> on 2014/08/14 19:38:12 UTC

[jira] [Commented] (HDFS-6801) Archival Storage: Add a new data migration tool

    [ https://issues.apache.org/jira/browse/HDFS-6801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14097260#comment-14097260 ] 

Vinayakumar B commented on HDFS-6801:
-------------------------------------

One quick comment.
FileStoragePolicy says its still needs implementation.

> 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)