hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo Nicholas Sze (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-6671) Archival Storage: Consider block storage policy in replicaiton
Date Thu, 17 Jul 2014 11:59:05 GMT

     [ 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

View raw message