[
https://issues.apache.org/jira/browse/HDFS-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961250#comment-15961250
]
Andrew Wang commented on HDFS-11633:
------------------------------------
Good catch! Yea, the clear is only supposed to clear things loaded from NN
metadata.
As an alternative fix, could we instead make the {{clear}} method a no-op, and
add a comment that we should only clear policies loaded from NN metadata?
HDFS-7337 will add pluggable policies that will be persisted and need to be
cleared.
> 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-alpha3
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Critical
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-11633.001.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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
