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/14 23:00:06 UTC

[jira] [Resolved] (HDFS-6677) Archival Storage: Change INodeFile and FSImage to support storage policy

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

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

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

Thanks Haohui for reviewing the patch.

I have committed this.

> Archival Storage: Change INodeFile and FSImage to support storage policy
> ------------------------------------------------------------------------
>
>                 Key: HDFS-6677
>                 URL: https://issues.apache.org/jira/browse/HDFS-6677
>             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: h6677_20140714.patch
>
>
> Policy ID will be stored in INodeFile header with 4 bits which can support 16 different storage policies.  The number of bits for replication will be reduced from 16 bits to 12 bits which is still able to support up to 4095 replicas.  The number of bits for block size remains 48 bits.  The memory usage of INodeFile remains unchanged.
> The storage policy IDs assigned to Hot, Warm and Cold policies are respectively 12, 8 and 4.  These numbers are chosen with gaps so that future policies can be added in-between.
> We should make a corresponding change in FSImage.



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