hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SammiChen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11268) Persist erasure coding policy ID in FSImage
Date Wed, 11 Jan 2017 01:33:58 GMT

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

SammiChen commented on HDFS-11268:
----------------------------------

Hi [~andrew.wang], I'am working on it. Will give an update soon. 

> Persist erasure coding policy ID in FSImage
> -------------------------------------------
>
>                 Key: HDFS-11268
>                 URL: https://issues.apache.org/jira/browse/HDFS-11268
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: erasure-coding
>    Affects Versions: 3.0.0-alpha1
>            Reporter: SammiChen
>            Assignee: SammiChen
>            Priority: Critical
>              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
(v6.3.4#6332)

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


Mime
View raw message