hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3342) SocketTimeoutException in BlockSender.sendChunks could have a better error message
Date Mon, 20 Oct 2014 18:08:33 GMT

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

Andrew Wang commented on HDFS-3342:
-----------------------------------

Hi Yongjun, thanks for working on this,

Looking at the new output you posted, it looks like it quashes the ERROR log, but we still
end up with 3 log prints for the same issue, and one is still at WARN. Wouldn't an ideal solution
print just a single log message at INFO? Also note that if someone has the log level set to
WARN (happens in production deployments), they'll see the scary stack trace but not the new
log print you added. It'd also be nice to not have stack trace spam in this situation, since
it's somewhat expected.

LMK what you think, thanks again.

> SocketTimeoutException in BlockSender.sendChunks could have a better error message
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-3342
>                 URL: https://issues.apache.org/jira/browse/HDFS-3342
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.0.0-alpha
>            Reporter: Todd Lipcon
>            Assignee: Yongjun Zhang
>            Priority: Minor
>              Labels: supportability
>         Attachments: HDFS-3342.001.patch
>
>
> Currently, if a client connects to a DN and begins to read a block, but then stops calling
read() for a long period of time, the DN will log a SocketTimeoutException "480000 millis
timeout while waiting for channel to be ready for write." This is because there is no "keepalive"
functionality of any kind. At a minimum, we should improve this error message to be an INFO
level log which just says that the client likely stopped reading, so disconnecting it.



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

Mime
View raw message