hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-4426) Secondary namenode shuts down immediately after startup
Date Wed, 23 Jan 2013 19:15:14 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Suresh Srinivas updated HDFS-4426:

    Attachment: HDFS-4426.branch-23.patch

Merging this change to 0.23 is not straight forward. Here is the merge patch that is slightly

Can some one quickly test this and +1 it?
If no one does it, I am going to commit it anyway in an hour, since it seems to be a simple
> 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,
> 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: 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

View raw message