[
https://issues.apache.org/jira/browse/HDFS-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316894#comment-14316894
]
Hadoop QA commented on HDFS-6348:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12698124/HDFS-6348.patch
against trunk revision b379972.
{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}. There were no new javadoc 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 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.balancer.TestBalancer
org.apache.hadoop.hdfs.TestDecommission
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9541//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9541//console
This message is automatically generated.
> Secondary namenode - RMI Thread prevents JVM from exiting after main()
> completes
> ---------------------------------------------------------------------------------
>
> Key: HDFS-6348
> URL: https://issues.apache.org/jira/browse/HDFS-6348
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.3.0
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 2.7.0
>
> Attachments: HDFS-6348.patch, HDFS-6348.patch,
> secondaryNN_threaddump_after_exit.log
>
>
> Secondary Namenode is not exiting when there is RuntimeException occurred
> during startup.
> Say I configured wrong configuration, due to that validation failed and
> thrown RuntimeException as shown below. But when I check the environment
> SecondaryNamenode process is alive. When analysed, RMI Thread is still alive,
> since it is not a daemon thread JVM is nit exiting.
> I'm attaching threaddump to this JIRA for more details about the thread.
> {code}
> java.lang.RuntimeException: java.lang.RuntimeException:
> java.lang.ClassNotFoundException: Class
> com.huawei.hadoop.hdfs.server.blockmanagement.MyBlockPlacementPolicy not found
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1900)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.BlockPlacementPolicy.getInstance(BlockPlacementPolicy.java:199)
> at
> org.apache.hadoop.hdfs.server.blockmanagement.BlockManager.<init>(BlockManager.java:256)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:635)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:260)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:205)
> at
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.main(SecondaryNameNode.java:695)
> Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException:
> Class com.huawei.hadoop.hdfs.server.blockmanagement.MyBlockPlacementPolicy
> not found
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1868)
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1892)
> ... 6 more
> Caused by: java.lang.ClassNotFoundException: Class
> com.huawei.hadoop.hdfs.server.blockmanagement.MyBlockPlacementPolicy not found
> at
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:1774)
> at
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:1866)
> ... 7 more
> 2014-05-07 14:27:04,666 INFO
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Stopping services
> started for active state
> 2014-05-07 14:27:04,666 INFO
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Stopping services
> started for standby state
> 2014-05-07 14:31:04,926 INFO
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode: STARTUP_MSG:
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
