[
https://issues.apache.org/jira/browse/HDFS-12054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071951#comment-16071951
]
lufei commented on HDFS-12054:
------------------------------
Maybe I didn't make it clear.I think this check is only useful for the kind of
EC operations like checkOperation(OperationCategory.{color:red}WRITE{color}).
The other kind of EC operations like
checkOperation(OperationCategory.{color:red}READ{color}) don't need this check.
HDFS-12066 solved the function of FSNamesystem#removeErasureCodingPolicy's
problem, so this issue only need to fix the FSNamesystem#addECPolicies's
problem.
[~jojochuang], sincerely look forward to your reply, thank you!
> FSNamesystem#addECPolicies should call checkNameNodeSafeMode() to ensure
> Namenode is not in safemode
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-12054
> URL: https://issues.apache.org/jira/browse/HDFS-12054
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.0.0-alpha3
> Reporter: lufei
> Assignee: lufei
> Labels: hdfs-ec-3.0-nice-to-have
> Attachments: HDFS-12054.001.patch
>
>
> In the process of FSNamesystem#addECPolicies, it would be better to call
> checkNameNodeSafeMode() to ensure NN is not in safemode.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
