[
https://issues.apache.org/jira/browse/HDFS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190528#comment-14190528
]
Hudson commented on HDFS-3342:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #6397 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/6397/])
HDFS-3342. SocketTimeoutException in BlockSender.sendChunks could have a better
error message. Contributed by Yongjun Zhang. (wang: rev
c2866ac34d063a4d2e150fe35632111b37a1514d)
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockSender.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataXceiver.java
> 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
> Fix For: 2.7.0
>
> Attachments: HDFS-3342.001.patch, HDFS-3342.002.patch,
> HDFS-3342.002.patch, HDFS-3342.003.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)
