Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6A71D200BC2 for ; Thu, 3 Nov 2016 06:57:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6938A160B0A; Thu, 3 Nov 2016 05:57:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AE1F3160AFB for ; Thu, 3 Nov 2016 06:57:00 +0100 (CET) Received: (qmail 29686 invoked by uid 500); 3 Nov 2016 05:56:59 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 29116 invoked by uid 99); 3 Nov 2016 05:56:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Nov 2016 05:56:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CE91B2C0087 for ; Thu, 3 Nov 2016 05:56:58 +0000 (UTC) Date: Thu, 3 Nov 2016 05:56:58 +0000 (UTC) From: "Mingliang Liu (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-11088) Quash unnecessary safemode WARN message during NameNode startup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 03 Nov 2016 05:57:01 -0000 [ 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: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org