hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Yiqun (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-9727) Improve the exception's log output in DataXceiver
Date Mon, 01 Feb 2016 03:07:39 GMT

     [ https://issues.apache.org/jira/browse/HDFS-9727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lin Yiqun updated HDFS-9727:
----------------------------
    Attachment: HDFS-9727.001.patch

> 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)

Mime
View raw message