[ https://issues.apache.org/jira/browse/HDFS-14396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910978#comment-16910978 ]
Yuxuan Wang commented on HDFS-14396: ------------------------------------ [~jojochuang] With HDFS-13596 , NN will not accept EC operation and also should not persist it until finalize is done. > Failed to load image from FSImageFile when downgrade from 3.x to 2.x > -------------------------------------------------------------------- > > Key: HDFS-14396 > URL: https://issues.apache.org/jira/browse/HDFS-14396 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Fei Hui > Assignee: Fei Hui > Priority: Major > Attachments: HDFS-14396.001.patch, HDFS-14396.002.patch > > > After fixing HDFS-13596, try to downgrade from 3.x to 2.x. But namenode can't > start because exception occurs. The message follows > {code:java} > 2019-01-23 17:22:18,730 ERROR org.apache.hadoop.hdfs.server.namenode.FSImage: > Failed to load image from > FSImageFile(file=/data1/hadoopdata/hadoop-namenode/current/fsimage_0000000000000025310, > cpktTxId=0000000000 > 000025310) > java.lang.NullPointerException > at > org.apache.hadoop.hdfs.server.namenode.FSImageFormatProtobuf$Loader.loadInternal(FSImageFormatProtobuf.java:243) > at > org.apache.hadoop.hdfs.server.namenode.FSImageFormatProtobuf$Loader.load(FSImageFormatProtobuf.java:179) > at > org.apache.hadoop.hdfs.server.namenode.FSImageFormat$LoaderDelegator.load(FSImageFormat.java:226) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:885) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:869) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:742) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:673) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:290) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:998) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:700) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:612) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:672) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:839) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:823) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1517) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1583) > 2019-01-23 17:22:19,023 WARN > org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Encountered exception > loading fsimage > java.io.IOException: Failed to load FSImage file, see error(s) above for more > info. > at > org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:688) > at > org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:290) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:998) > at > org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:700) > at > org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:612) > {code} > This issue occurs because 3.x namenode saves image with EC fields during > upgrade > Try to fix it -- This message was sent by Atlassian Jira (v8.3.2#803003) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org