[
https://issues.apache.org/jira/browse/HDFS-5368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796710#comment-13796710
]
Hadoop QA commented on HDFS-5368:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12608692/HDFS-5368.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/5209//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/5209//console
This message is automatically generated.
> Namenode deadlock during safemode extention
> -------------------------------------------
>
> Key: HDFS-5368
> URL: https://issues.apache.org/jira/browse/HDFS-5368
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Vinay
> Assignee: Vinay
> Priority: Blocker
> Attachments: HDFS-5368.patch, NN-deadlock.zip
>
>
> Namenode entered to safemode during restart
> 1. After restart NN entered to safemode extention.
> 2. During this time deadlock happened between datanode heartbeat and
> SafemodeMonitor() thread.
> Found one Java-level deadlock:
> =============================
> "org.apache.hadoop.hdfs.server.namenode.FSNamesystem$SafeModeMonitor@9fe953":
> waiting to lock monitor 0x18c3b42c (object 0x0439c6f8, a java.util.TreeMap),
> which is held by "IPC Server handler 2 on 62212"
> "IPC Server handler 2 on 62212":
> waiting to lock monitor 0x18c3987c (object 0x043849a0, a
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem$SafeModeInfo),
> which is held by
> "org.apache.hadoop.hdfs.server.namenode.FSNamesystem$SafeModeMonitor@9fe953"
> Check attached jstack for complete stack
--
This message was sent by Atlassian JIRA
(v6.1#6144)
