Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 451D718C46 for ; Mon, 1 Feb 2016 03:07:40 +0000 (UTC) Received: (qmail 213 invoked by uid 500); 1 Feb 2016 03:07:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 156 invoked by uid 500); 1 Feb 2016 03:07:39 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 133 invoked by uid 99); 1 Feb 2016 03:07:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Feb 2016 03:07:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id C6B9B2C044E for ; Mon, 1 Feb 2016 03:07:39 +0000 (UTC) Date: Mon, 1 Feb 2016 03:07:39 +0000 (UTC) From: "Lin Yiqun (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-9727) Improve the exception's log output in DataXceiver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-9727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Yiqun updated HDFS-9727: ---------------------------- Status: Patch Available (was: Open) Attach a initial patch, kindly review. > Improve the exception's log output in DataXceiver > ------------------------------------------------- > > Key: HDFS-9727 > URL: https://issues.apache.org/jira/browse/HDFS-9727 > Project: Hadoop HDFS > Issue Type: Improvement > Affects Versions: 2.7.1 > Reporter: Lin Yiqun > Assignee: Lin Yiqun > Priority: Minor > Attachments: HDFS-9727.001.patch > > > There are some not appropriate logLevel output in many palaces of {{DataXceiver}}. When some exceptions happened, the output logLevel often the info level not warn. Like these: > {code} > try { > blockSender = new BlockSender(block, blockOffset, length, > true, false, sendChecksum, datanode, clientTraceFmt, > cachingStrategy); > } catch(IOException e) { > String msg = "opReadBlock " + block + " received exception " + e; > LOG.info(msg); > sendResponse(ERROR, msg); > throw e; > } > {code} > And this case is not only one, it looks frequent in DataXceiver methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)