[
https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714875#comment-13714875
]
Suresh Srinivas commented on HDFS-5016:
---------------------------------------
I think throwing an IOException seems unnecessary. As I described earlier, in
this case, writer can be interrupted successfully, since it is reading the
socket and socket timeout can be configured for reads. So join called on writer
thread should not block. That is not the case with responder that is writing to
a socket.
Since writer can be interrupted successfully, no more block data is received
and hence no further change can occur to the block.
> Heartbeating thread blocks under some failure conditions leading to loss of
> datanodes
> -------------------------------------------------------------------------------------
>
> Key: HDFS-5016
> URL: https://issues.apache.org/jira/browse/HDFS-5016
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Suresh Srinivas
> Priority: Blocker
> Fix For: 2.1.0-beta
>
> Attachments: HDFS-5016.patch, jstack1.txt
>
>
> In the testing of some failure scenarios for HBase MTTR, we have been
> simulating node failures via firewalling of nodes (where all communication
> ports would be firewalled except ssh's port). We have noticed that when a
> (data)node is firewalled, we lose certain other datanodes - those that were
> involved in some communication with the firewalled node before the latter was
> firewalled. Will attach jstack output from one of the lost datanodes. The
> heartbeating thread seems to be locked up.
> This jira is to track a fix for the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
