[HADOOP-3269] NameNode doesn't startup when restarted after running an MR job

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.18.0
• Fix Version/s: 0.18.0
• Assignee: Tsz-wo Sze
• Reporter: Devaraj Das
• Created: 17/Apr/08 18:25
• Updated: 22/Aug/08 19:50
• Resolved: 18/Apr/08 09:08

Description

If the following is done in sequence the namenode doesn't start up (tried all these on a single node cluster setup)

1) Build a fresh hadoop jar from trunk

2) bin/start-all.sh

3) bin/hadoop dfs -put <somedir> input

4) bin/hadoop jar build/hadoop-0.18.0-dev-examples.jar wordcount input output

5) bin/stop-all.sh

6) bin/start-all.sh

Namenode doesnt start up. It fails with following exception:
2008-04-17 16:05:32,852 ERROR org.apache.hadoop.dfs.NameNode:
org.apache.hadoop.fs.permission.AccessControlException: ugi = null
at org.apache.hadoop.dfs.PermissionChecker.<init>(PermissionChecker.java:49)
at org.apache.hadoop.dfs.FSNamesystem.checkPermission(FSNamesystem.java:4188)
at org.apache.hadoop.dfs.FSNamesystem.checkTraverse(FSNamesystem.java:4167)
at org.apache.hadoop.dfs.FSNamesystem.getFileInfo(FSNamesystem.java:1554)
at org.apache.hadoop.dfs.FSNamesystem.changeLease(FSNamesystem.java:4358)
at org.apache.hadoop.dfs.FSEditLog.loadFSEdits(FSEditLog.java:590)
at org.apache.hadoop.dfs.FSImage.loadFSEdits(FSImage.java:843)
at org.apache.hadoop.dfs.FSImage.loadFSImage(FSImage.java:717)
at org.apache.hadoop.dfs.FSImage.recoverTransitionRead(FSImage.java:281)
at org.apache.hadoop.dfs.FSDirectory.loadFSImage(FSDirectory.java:81)
at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:274)
at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:255)
at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:133)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:178)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:164)
at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:782)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:791)