[
https://issues.apache.org/jira/browse/HDFS-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183118#comment-14183118
]
Hadoop QA commented on HDFS-3342:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676920/HDFS-3342.003.patch
against trunk revision 0942c99.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8521//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8521//console
This message is automatically generated.
> 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, 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)
