Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 17 Dec 2015 02:29:46 +0000 (UTC)
From: "Yongjun Zhang (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12922571.1450319357000.48731.1450319386605@Atlassian.JIRA>
In-Reply-To: <JIRA.12922571.1450319357000@Atlassian.JIRA>
References: <JIRA.12922571.1450319357000@Atlassian.JIRA>
 <JIRA.12922571.1450319357649@arcas>
Subject: [jira] [Created] (HDFS-9569) Change msg issused before loading
 fsimage to Info from debug for better supportability
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Yongjun Zhang created HDFS-9569:
-----------------------------------

             Summary: Change msg issused before loading fsimage to Info from debug for better supportability
                 Key: HDFS-9569
                 URL: https://issues.apache.org/jira/browse/HDFS-9569
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
            Reporter: Yongjun Zhang
            Assignee: Yongjun Zhang
            Priority: Trivial


When NN starts to load fsimage, it does

{code}
 void loadFSImageFile(FSNamesystem target, MetaRecoveryContext recovery,
      FSImageFile imageFile, StartupOption startupOption) throws IOException {
      LOG.debug("Planning to load image :\n" + imageFile);
      ......
    long txId = loader.getLoadedImageTxId();
    LOG.info("Loaded image for txid " + txId + " from " + curFile);
{code}

A debug msg is issued at the beginning with the fsimage file name, then at the end an info msg is issued after loading.

If the fsimage loading failed due to corrupted fsimage, we don't see the first msg. It'd be helpful to always be able to see from NN logs what fsimage file it's loading.

Creating this jira to change the debug to info.

{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)