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

Posted to hdfs-dev@hadoop.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2014/07/17 13:59:05 UTC

[jira] [Resolved] (HDFS-6671) Archival Storage: Consider block storage policy in replicaiton

     [ https://issues.apache.org/jira/browse/HDFS-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo Nicholas Sze resolved HDFS-6671.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: Archival Storage (HDFS-6584)
     Hadoop Flags: Reviewed

Thanks Vinay for reviewing the patches.

I have committed this.

> Archival Storage: Consider block storage policy in replicaiton
> --------------------------------------------------------------
>
>                 Key: HDFS-6671
>                 URL: https://issues.apache.org/jira/browse/HDFS-6671
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>             Fix For: Archival Storage (HDFS-6584)
>
>         Attachments: h6671_20140714.patch, h6671_20140715.patch, h6671_20140715b.patch, h6671_20140715c.patch, h6671_20140717.patch
>
>
> In order to satisfy storage policy requirement, replication monitor in addition reads storage policy information from INodeFile when performing replication.  As before, it only adds replicas if a block is under replicated, and deletes replicas if a block is over replicated.  It will NOT move replicas around for satisfying storage policy requirement.



--
This message was sent by Atlassian JIRA
(v6.2#6252)