hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-7005) DFS input streams do not timeout
Date Fri, 05 Sep 2014 20:18:34 GMT
Daryn Sharp created HDFS-7005:

             Summary: 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: 2.5.0, 3.0.0
            Reporter: Daryn Sharp
            Assignee: Daryn Sharp
            Priority: Critical

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