[
https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720337#comment-13720337
]
Suresh Srinivas commented on HDFS-5016:
---------------------------------------
bq. We probably don't want to stick the entire stack trace in the IOException
msg. Same for BlockReceiver.
Can you explain why it is not a good idea? Note that this issue should happen
quite rarely.
As regards to your other comment, you want some thing like this?
{code}
String msg = "Join on responder thread " + responder
+ " timed out\n" + StringUtils.getStackTrace(responder);
{code}
> 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.1.patch, HDFS-5016.2.patch, 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
