hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei-Chiu Chuang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11268) Persist erasure coding policy ID in FSImage
Date Tue, 27 Dec 2016 22:13:58 GMT

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

Wei-Chiu Chuang commented on HDFS-11268:

I thought EC policy ID is stored using replication factor field, no?

> Persist erasure coding policy ID in FSImage
> -------------------------------------------
>                 Key: HDFS-11268
>                 URL: https://issues.apache.org/jira/browse/HDFS-11268
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 3.0.0-alpha1
>            Reporter: SammiChen
>            Assignee: SammiChen
>              Labels: hdfs-ec-3.0-must-do
> Currently, FSImage only has the information about whether the file is striped or not.
It doesn't save the erasure coding policy ID. Later, when the FSImage is loaded to create
the name space, the default system ec policy is used to as file's ec policy.  In case if the
ec policy on file is not the default ec policy, then the content of the file cannot be accessed
correctly in this case. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message