[HDFS-4426] Secondary namenode shuts down immediately after startup

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha, 0.23.6
• Fix Version/s: 2.0.3-alpha, 0.23.6, 0.23.7
• Component/s: namenode
• Assignee: Arpit Agarwal
• Reporter: Jason Darrell Lowe
• Created: 22/Jan/13 19:57
• Updated: 15/Feb/13 13:12
• Resolved: 23/Jan/13 19:12

Description

After HADOOP-9181 went in, the secondary namenode immediately shuts down after it is started. From the startup logs:

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
************************************************************/

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.

Issue Links

• is related to: HDFS-4430 Add a test case for NameNode/SecondaryNameNode startup
• is related to: HADOOP-9181 Set daemon flag for HttpServer's QueuedThreadPool
• relates to: HDFS-2896 The 2NN incorrectly daemonizes