[ https://issues.apache.org/jira/browse/HDFS-7005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505739#comment-14505739 ]
Karthik Kambatla commented on HDFS-7005: ---------------------------------------- Thanks for the ping, [~cnauroth]. [~ndimiduk] - there are no active plans for 2.5.3. If HDFS committers think this issue is serious enough to warrant a point release, I don't mind creating the RC and putting it through a vote. > 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 > Fix For: 2.6.0 > > 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 (v6.3.4#6332)