[
https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714851#comment-13714851
]
Hadoop QA commented on HDFS-5016:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12593439/HDFS-5016.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4702//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4702//console
This message is automatically generated.
> 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
