[
https://issues.apache.org/jira/browse/HDFS-11268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang updated HDFS-11268:
-------------------------------
Priority: Critical (was: Major)
Component/s: erasure-coding
Issue Type: Bug (was: Improvement)
Hi [~Sammi] have you made any progress on this issue? I'm changing this to Bug
and Critical, since it seems important for EC users.
> 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: [email protected]
For additional commands, e-mail: [email protected]
