hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1918) DataXceiver double logs every IOE out of readBlock
Date Thu, 12 May 2011 07:03:48 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032280#comment-13032280

Todd Lipcon commented on HDFS-1918:

Hmm, I half agree with your assessment. But, I think this patch will change the metrics behavior
here, no?

Maybe we still need to catch certain classes of exception (socket timeout and connection reset
by peer) and treat them as successful block reads as far as metrics are concerned? (And probably
log at DEBUG level instead of WARN)?

> DataXceiver double logs every IOE out of readBlock
> --------------------------------------------------
>                 Key: HDFS-1918
>                 URL: https://issues.apache.org/jira/browse/HDFS-1918
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.20.2
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Trivial
>             Fix For: 0.22.0
>         Attachments: HDFS-1918.patch
> DataXceiver will log an IOE twice because opReadBlock() will catch it, log a WARN, then
throw it again only to be caught in run() as a Throwable and logged as an ERROR. As far as
I can tell all the information is the same in both messages.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message