You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Yongjun Zhang (JIRA)" <ji...@apache.org> on 2014/10/05 20:01:34 UTC

[jira] [Updated] (HDFS-3342) SocketTimeoutException in BlockSender.sendChunks could have a better error message

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

Yongjun Zhang updated HDFS-3342:
--------------------------------
    Attachment: HDFS-3342.001.patch

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