Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

NameNode Last CheckPoint is not triggering correctly based checkpoint period and transactions in HDP 2.6.5?

NameNode Last CheckPoint is not triggering correctly based checkpoint period and transactions in HDP 2.6.5?

Super Collaborator

Hello Team,

we are observing NameNode Last checkpoint alert is continuously appearing in Ambari UI. we have checked Timeperiod and Transaction properties for Namenode checkpoint looks fine. in secondary Namenode Log we getting below error:

2018-09-20 08:58:53,275 ERROR namenode.SecondaryNameNode (SecondaryNameNode.java:doWork(409)) - Exception in doCheckpoint

java.io.IOException: Inconsistent checkpoint fields.

LV = -63 namespaceID = 156032726 cTime = 0 ; clusterId = CID-a68bebda-c84a-4599-ba9c-fb5a77ba5c44 ; blockpoolId = BP-436455769-10.74.144.26-1533308885101.

Expecting respectively: -63; 444167579; 0; CID-11fb5fdb-8c80-416e-bf88-0d68b0b8b96d; BP-1567627602-10.74.144.26-1524757739170.

at org.apache.hadoop.hdfs.server.namenode.CheckpointSignature.validateStorageInfo(CheckpointSignature.java:143)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:541)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doWork(SecondaryNameNode.java:405)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$1.run(SecondaryNameNode.java:371)

at org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:476)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.run(SecondaryNameNode.java:367)

at java.lang.Thread.run(Thread.java:748)

2018-09-20 08:59:53,322 ERROR namenode.SecondaryNameNode (SecondaryNameNode.java:doWork(409)) - Exception in doCheckpoint

java.io.IOException: Inconsistent checkpoint fields.

LV = -63 namespaceID = 156032726 cTime = 0 ; clusterId = CID-a68bebda-c84a-4599-ba9c-fb5a77ba5c44 ; blockpoolId = BP-436455769-10.74.144.26-1533308885101.

Expecting respectively: -63; 444167579; 0; CID-11fb5fdb-8c80-416e-bf88-0d68b0b8b96d; BP-1567627602-10.74.144.26-1524757739170.

at org.apache.hadoop.hdfs.server.namenode.CheckpointSignature.validateStorageInfo(CheckpointSignature.java:143)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:541)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doWork(SecondaryNameNode.java:405)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$1.run(SecondaryNameNode.java:371)

at org.apache.hadoop.security.SecurityUtil.doAsLoginUserOrFatal(SecurityUtil.java:476)

at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.run(SecondaryNameNode.java:367)

Any one knows how to resolve this issue?

Don't have an account?
Coming from Hortonworks? Activate your account here