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] [Updated] (HDFS-7005) DFS input streams do not timeout
Date Mon, 08 Sep 2014 15:05:29 GMT

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

Daryn Sharp updated HDFS-7005:
    Status: Patch Available  (was: Open)

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