Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
5694 2018-01-30 15:55:47,530 WARN [Thread-67] datanode.BPServiceActor(849): Unexpected exception in block pool Block pool <registering> (Datanode Uuid e3f356a4-76ff-4aee-a98f-b316672a35e7) service to localhost/127.0.0.1:57626 5695 java.lang.NoClassDefFoundError: Could not initialize class com.fasterxml.jackson.databind.ObjectMapper 5696 at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsVolumeImpl.<clinit>(FsVolumeImpl.java:105) 5697 at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsVolumeImplBuilder.build(FsVolumeImplBuilder.java:70) 5698 at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl.addVolume(FsDatasetImpl.java:428) 5699 at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetImpl.<init>(FsDatasetImpl.java:318) 5700 at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetFactory.newInstance(FsDatasetFactory.java:34) 5701 at org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.FsDatasetFactory.newInstance(FsDatasetFactory.java:30) 5702 at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage(DataNode.java:1703) 5703 at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool(DataNode.java:1650) 5704 at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo(BPOfferService.java:376) 5705 at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.connectToNNAndHandshake(BPServiceActor.java:280) 5706 at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:816) 5707 at java.lang.Thread.run(Thread.java:748)
Looks like a jackson version conflict is causing the MiniDFSCluster to crash. There's a new shaded jar out of Hadoop3 which should help this.