[
https://issues.apache.org/jira/browse/HDFS-9727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127501#comment-15127501
]
Mingliang Liu commented on HDFS-9727:
-------------------------------------
Specifically, {{hadoop.hdfs.TestRecoverStripedFile}} seems flaky and is tracked
by [HDFS-9716].
> 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, HDFS-9727.002.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)
