[
https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690852#comment-13690852
]
Chris Nauroth commented on HDFS-4927:
-------------------------------------
Here is the stack trace that I see on namenode startup.
{code}
2013-06-21 15:30:26,045 ERROR [main] namenode.FSEditLogLoader
(FSEditLogLoader.java:loadEditRecords(198)) - Encountered exception on
operation MkdirOp [length=0, inodeId=0, path=/createdViaInjectingInEditsLog,
timestamp=0, permissions=joeDoe:people:rwxrwxrwx, opCode=OP_MKDIR, txid=2]
java.io.IOException: The layout version -45 supports inodeId but gave bogus
inodeId
at
org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.getAndUpdateLastInodeId(FSEditLogLoader.java:256)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.applyEditLogOp(FSEditLogLoader.java:414)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:193)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:106)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.loadEdits(FSImage.java:736)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:650)
at
org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:267)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:703)
at
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:537)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:416)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:455)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:648)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:633)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1213)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1279)
{code}
> CreateEditsLog creates inodes with an invalid inode ID, which then cannot be
> loaded by a namenode.
> --------------------------------------------------------------------------------------------------
>
> Key: HDFS-4927
> URL: https://issues.apache.org/jira/browse/HDFS-4927
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode, test
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Chris Nauroth
>
> {{CreateEditsLog#addFiles}} always creates inodes with ID hard-coded to
> {{INodeId#GRANDFATHER_INODE_ID}}. At initialization time, namenode will not
> load the resulting edits, because this is an invalid inode ID.
--
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
