hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3269) NameNode doesn't startup when restarted after running an MR job
Date Thu, 17 Apr 2008 22:07:23 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590219#action_12590219
] 

dhruba borthakur commented on HADOOP-3269:
------------------------------------------

+1. Code looks good.

> NameNode doesn't startup when restarted after running an MR job
> ---------------------------------------------------------------
>
>                 Key: HADOOP-3269
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3269
>             Project: Hadoop Core
>          Issue Type: Bug
>    Affects Versions: 0.18.0
>            Reporter: Devaraj Das
>            Assignee: Tsz Wo (Nicholas), SZE
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: 3269_20080417.patch
>
>
> 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)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message