[
https://issues.apache.org/jira/browse/HDFS-11268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769045#comment-15769045
]
Kai Zheng commented on HDFS-11268:
----------------------------------
This was exposed by HDFS-11152. [~Sammi], do you find a good place to store the
policy ID? This should be a must since we have various erasure coding policies
other than just the default one.
bq. FSImage only has the information about whether the file is striped or not.
Not checking the codes yet, but what's the type used to store the 'boolean'
info regarding {{is striped or not}}?
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
