8.3.1. Known issues for HDFS

  • BUG-14542: HDP 2.1 exception during namenode service work.

    Problem: After the start of the NameNode service, the following exception occurred:

    2014-03-06 14:03:03,586 INFO org.apache.hadoop.hdfs.server.namenode.FSImageFormatProtobuf: Loaded FSImage in 2 seconds. 
    2014-03-06 14:03:03,586 INFO org.apache.hadoop.hdfs.server.namenode.FSImage: Loaded image for txid 0 from C:\hdpdata\hdfs\nn\current\fsimage_0000000000000000000 
    2014-03-06 14:03:03,680 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Need to save fs image? false (staleImage=false, haEnabled=false, isRollingUpgrade=false) 
    2014-03-06 14:03:03,680 INFO org.apache.hadoop.hdfs.server.namenode.FSEditLog: Starting log segment at 1 
    2014-03-06 14:03:05,273 INFO org.apache.hadoop.hdfs.server.namenode.NameCache: initialized with 0 entries 0 lookups 
    2014-03-06 14:03:05,273 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Finished loading FSImage in 5703 msecs 
    2014-03-06 14:03:08,883 INFO org.apache.hadoop.hdfs.server.namenode.NameNode: RPC server is binding to VMG22:8020 
    2014-03-06 14:03:08,898 INFO org.apache.hadoop.ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue 
    2014-03-06 14:03:08,930 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join 
    java.lang.IllegalArgumentException: No enum const class org.apache.hadoop.security.SaslRpcServer$QualityOfProtection.NONE 
         9 more