[
https://issues.apache.org/jira/browse/HDFS-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561589#comment-13561589
]
Hudson commented on HDFS-4426:
------------------------------
Integrated in Hadoop-Hdfs-0.23-Build #504 (See
[https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/504/])
HDFS-4426. Merge change 1437627 from trunk. (Revision 1437650)
Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1437650
Files :
*
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/branches/branch-0.23/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/SecondaryNameNode.java
> 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
> Fix For: 2.0.3-alpha, 0.23.6
>
> Attachments: HDFS-4426.1.patch, HDFS-4426.branch-23.patch,
> 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
