hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7005) DFS input streams do not timeout
Date Mon, 08 Sep 2014 17:54:29 GMT

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

Hadoop QA commented on HDFS-7005:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision 0974f43.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {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:red}-1 core tests{color}.  The patch failed these 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/7948//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7948//console

This message is automatically generated.

> DFS input streams do not timeout
> --------------------------------
>                 Key: HDFS-7005
>                 URL: https://issues.apache.org/jira/browse/HDFS-7005
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 3.0.0, 2.5.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Critical
>         Attachments: HDFS-7005.patch
> Input streams lost their timeout.  The problem appears to be {{DFSClient#newConnectedPeer}}
does not set the read timeout.  During a temporary network interruption the server will close
the socket, unbeknownst to the client host, which blocks on a read forever.
> The results are dire.  Services such as the RM, JHS, NMs, oozie servers, etc all need
to be restarted to recover - unless you want to wait many hours for the tcp stack keepalive
to detect the broken socket.

This message was sent by Atlassian JIRA

View raw message