Description
I want upgrade an old cluster(0.20.2-cdh3u1) to trunk instance,
I can upgrade successfully if I don't configurage HA, but if HA enabled,
there is NPE when I run ' hdfs namenode -initializeSharedEdits'
14/03/20 15:06:41 INFO namenode.FSNamesystem: Retry cache on namenode is enabled 14/03/20 15:06:41 INFO namenode.FSNamesystem: Retry cache will use 0.03 of total heap and retry cache entry expiry time is 600000 millis 14/03/20 15:06:41 INFO util.GSet: Computing capacity for map NameNodeRetryCache 14/03/20 15:06:41 INFO util.GSet: VM type = 64-bit 14/03/20 15:06:41 INFO util.GSet: 0.029999999329447746% max memory 896 MB = 275.3 KB 14/03/20 15:06:41 INFO util.GSet: capacity = 2^15 = 32768 entries 14/03/20 15:06:41 INFO namenode.AclConfigFlag: ACLs enabled? false 14/03/20 15:06:41 INFO common.Storage: Lock on /data/hadoop/data1/dfs/name/in_use.lock acquired by nodename 7326@10-150-170-176 14/03/20 15:06:42 INFO common.Storage: Lock on /data/hadoop/data2/dfs/name/in_use.lock acquired by nodename 7326@10-150-170-176 14/03/20 15:06:42 INFO namenode.FSImage: No edit log streams selected. 14/03/20 15:06:42 INFO namenode.FSImageFormatPBINode: Loading 1 INodes. 14/03/20 15:06:42 FATAL namenode.NameNode: Exception in namenode join java.lang.NullPointerException at org.apache.hadoop.hdfs.server.namenode.FSDirectory.isReservedName(FSDirectory.java:2984) at org.apache.hadoop.hdfs.server.namenode.FSImageFormatPBINode$Loader.addToParent(FSImageFormatPBINode.java:205) at org.apache.hadoop.hdfs.server.namenode.FSImageFormatPBINode$Loader.loadINodeDirectorySection(FSImageFormatPBINode.java:162) 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:168) at org.apache.hadoop.hdfs.server.namenode.FSImageFormat$LoaderDelegator.load(FSImageFormat.java:120) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:895) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:881) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:704) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:642) at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:271) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:894) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:653) at org.apache.hadoop.hdfs.server.namenode.NameNode.initializeSharedEdits(NameNode.java:912) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1276) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1360) 14/03/20 15:06:42 INFO util.ExitUtil: Exiting with status 1 14/03/20 15:06:42 INFO namenode.NameNode: SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down NameNode at 10-150-170-176/10.150.170.176 ************************************************************/
Attachments
Attachments
Issue Links
- relates to
-
HDFS-5988 Bad fsimage always generated after upgrade
-
- Closed
-