[
https://issues.apache.org/jira/browse/HDFS-11088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15631719#comment-15631719
]
Mingliang Liu commented on HDFS-11088:
--------------------------------------
I think the proposal and the solution make sense. Thanks for pinging me
[~andrew.wang].
{quote}
I think we can file another JIRA to make a change if we think it's necessary to
do here. This JIRA will be better to focus on the change as the this JIRA's
title mentioned.
{quote}
I think we should add the check in this patch as it is needed largely because
we're changing the "force" parameter in {{activate()}}. If "force" is true as
it was, we can ignore the return value blindly in that it is supposed to return
true after leaving safe mode ignoring the orphan blocks (if any); here it
becomes false, we'd better add Precondition check on the return value for
safety.
> 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, HDFS-11088.002.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: [email protected]
For additional commands, e-mail: [email protected]
