[
https://issues.apache.org/jira/browse/HDFS-14529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970102#comment-16970102
]
Stephen O'Donnell commented on HDFS-14529:
------------------------------------------
[~hexiaoqiao] The stack trace you posted looks like HDFS-12369. See this
comment especially, as we believe HDFS-12369 can show some different stack
traces when it occurs:
https://issues.apache.org/jira/browse/HDFS-12369?focusedCommentId=16304855&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16304855
[~szetszwo] I encountered the stack you mentioned once in a cluster that has
snapshots, and the snapshots were somewhat corrupt. The cluster had frequently
hit HDFS-13101. In that example, we found the file it was attempting to apply
the TimesOp against did not exist except in the snapshot, and if I recall
correctly, within the snapshot it was not really readable due to something
similar to HDFS-13101. The interesting thing, was that even though the file was
deleted, more edits kept appearing with the invalid TimesOp in it. That cluster
had other issues we fixed and this problem got cleared as a side-effect. In
short, it is likely this is somehow related to snapshots.
> NPE while Loading the Editlogs
> ------------------------------
>
> Key: HDFS-14529
> URL: https://issues.apache.org/jira/browse/HDFS-14529
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 3.1.1
> Reporter: Harshakiran Reddy
> Assignee: Ayush Saxena
> Priority: Major
>
> {noformat}
> 2019-05-31 15:15:42,397 ERROR namenode.FSEditLogLoader: Encountered exception
> on operation TimesOp [length=0,
> path=/testLoadSpace/dir0/dir0/dir0/dir2/_file_9096763, mtime=-1,
> atime=1559294343288, opCode=OP_TIMES, txid=18927893]
> java.lang.NullPointerException
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirAttrOp.unprotectedSetTimes(FSDirAttrOp.java:490)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.applyEditLogOp(FSEditLogLoader.java:711)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:286)
> at
> org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:181)
> at org.apache.hadoop.hdfs.server.namenode.FSImage.loadEdits(FSImage.java:924)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:771)
> at
> org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:331)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1105)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:726)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.doRecovery(NameNode.java:1558)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1640)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1725){noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
