[
https://issues.apache.org/jira/browse/HDFS-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560413#comment-13560413
]
Hadoop QA commented on HDFS-4426:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566086/HDFS-4426.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:red}-1 findbugs{color}. The patch appears to introduce 2 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/3871//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/3871//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3871//console
This message is automatically generated.
> Secondary namenode shuts down immediately after startup
> -------------------------------------------------------
>
> Key: HDFS-4426
> URL: https://issues.apache.org/jira/browse/HDFS-4426
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.0.3-alpha, 0.23.6
> Reporter: Jason Lowe
> Assignee: Arpit Agarwal
> Priority: Blocker
> Attachments: HDFS-4426.patch, HDFS-4426.patch, HDFS-4426.patch
>
>
> After HADOOP-9181 went in, the secondary namenode immediately shuts down
> after it is started. From the startup logs:
> {noformat}
> 2013-01-22 19:54:28,826 INFO namenode.SecondaryNameNode
> (SecondaryNameNode.java:initialize(299)) - Checkpoint Period :3600 secs (60
> min)
> 2013-01-22 19:54:28,826 INFO namenode.SecondaryNameNode
> (SecondaryNameNode.java:initialize(301)) - Log Size Trigger :40000 txns
> 2013-01-22 19:54:28,845 INFO namenode.SecondaryNameNode
> (StringUtils.java:run(616)) - SHUTDOWN_MSG:
> /************************************************************
> SHUTDOWN_MSG: Shutting down SecondaryNameNode at xx
> ************************************************************/
> {noformat}
> I looked into the issue, and it's shutting down because
> SecondaryNameNode.main starts a bunch of daemon threads then returns. With
> nothing but daemon threads remaining, the JVM sees no reason to keep going
> and proceeds to shutdown. Apparently we were implicitly relying on the fact
> that the HttpServer QueuedThreadPool threads were not daemon threads to keep
> the secondary namenode process up.
--
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
