[
https://issues.apache.org/jira/browse/HDFS-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112998#comment-17112998
]
Rungroj Maipradit commented on HDFS-11633:
------------------------------------------
The 002 patch by [~weichiu] seems to be prepared as a workaround for HDFS-7337.
Now HDFS-7337 had been resolved. Will "enabledPoliciesByName.clear();" come
back to the clear function? I also mentioned this issue in HDFS-15361.
> FSImage failover disables all erasure coding policies
> ------------------------------------------------------
>
> Key: HDFS-11633
> URL: https://issues.apache.org/jira/browse/HDFS-11633
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: erasure-coding, namenode
> Affects Versions: 3.0.0-alpha4
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Critical
> Labels: hdfs-ec-3.0-must-do
> Fix For: 3.0.0-alpha4
>
> Attachments: HDFS-11633.001.patch, HDFS-11633.002.patch,
> HDFS-11633.test.patch
>
>
> If NameNode fails to load the fsimage in the first NameNode metadata
> directory, it accidentally clears all enabled erasure coding policies in
> ErasureCodingPolicyManager.
> Even if the NameNode configures multiple fsimage metadata directory and it
> successfully loads the second one, enabled erasure coding policies are not
> restored.
> In the current implementation, we do not have a ErasureCodingPolicyManager
> section in fsimage, so a fsimage reload does not reload ECPM.
> The easiest fix before ECPM section is implemented, is don't clear ECPM when
> FSNamesystem is cleared.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
