[
https://issues.apache.org/jira/browse/HDFS-6348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526881#comment-14526881
]
Hadoop QA commented on HDFS-6348:
---------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 14m 35s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | 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{color} | javac | 7m 28s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 35s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 22s | The applied patch does
not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle | 2m 21s | There were no new checkstyle
issues. |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 36s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 3m 5s | The patch does not introduce
any new Findbugs (version 2.0.3) warnings. |
| {color:green}+1{color} | native | 3m 13s | Pre-build of native portion |
| {color:green}+1{color} | hdfs tests | 183m 49s | Tests passed in hadoop-hdfs.
|
| | | 226m 47s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12730177/HDFS-6348-003.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / bb9ddef |
| hadoop-hdfs test log |
https://builds.apache.org/job/PreCommit-HDFS-Build/10781/artifact/patchprocess/testrun_hadoop-hdfs.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HDFS-Build/10781/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-HDFS-Build/10781/console |
This message was 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
> Attachments: HDFS-6348-003.patch, 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)
