[
https://issues.apache.org/jira/browse/HDFS-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631159#comment-15631159
]
Andrew Wang commented on HDFS-11088:
------------------------------------
This looks okay, since {{checkSafeMode}} behaves very similarly. It's a bit
concerning though that we don't check the return value; I think
{{numberOfBytesInFutureBlocks}} will always be zero here since no block reports
have been received so {{force}} doesn't apply, but maybe we should add a
Precondition check on the return value for safety.
[~liuml07] / [~jingzhao] care to comment as the local safemode experts?
> Quash unnecessary safemode WARN message during NameNode startup
> ---------------------------------------------------------------
>
> Key: HDFS-11088
> URL: https://issues.apache.org/jira/browse/HDFS-11088
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha1
> Reporter: Andrew Wang
> Assignee: Yiqun Lin
> Priority: Trivial
> Labels: newbie
> Attachments: HDFS-11088.001.patch
>
>
> I tried starting a NameNode on a freshly formatted cluster, and it produced
> this WARN log:
> {noformat}
> 16/11/01 16:42:44 WARN blockmanagement.BlockManagerSafeMode: forceExit used
> when normal exist would suffice. Treating force exit as normal safe mode exit.
> {noformat}
> I didn't do any special commands related to safemode, so this log should be
> quashed.
> I didn't try the branch-2's, but it's likely this issue exists there as well.
--
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
