hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongjun Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3342) SocketTimeoutException in BlockSender.sendChunks could have a better error message
Date Sun, 05 Oct 2014 18:01:34 GMT

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

Yongjun Zhang updated HDFS-3342:
--------------------------------
    Status: Patch Available  (was: Open)

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

Mime
View raw message