Checkpoint Status on name node

[#1]

I keep getting the follwoing health error message:

The filesystem checkpoint is 22 hour(s), 40 minute(s) old. This is 2,267.75% of the configured checkpoint period of 1 hour(s). Critical threshold: 400.00%. 10,775 transactions have occurred since the last filesystem checkpoint. This is 1.08% of the configured checkpoint transaction target of 1,000,000.

What is causing this and how can I get it to stop.

Logs:

Number of transactions: 8 Total time for transactions(ms): 1 Number of transactions batched in Syncs: 0 Number of syncs: 6 SyncTimes(ms): 132 

Number of transactions: 8 Total time for transactions(ms): 1 Number of transactions batched in Syncs: 0 Number of syncs: 7 SyncTimes(ms): 155 

Finalizing edits file /dfs/nn/current/edits_inprogress_0000000000000021523 -> /dfs/nn/current/edits_0000000000000021523-0000000000000021530

Starting log segment at 21531

Rescanning after 30000 milliseconds

Scanned 0 directive(s) and 0 block(s) in 0 millisecond(s).

list corrupt file blocks returned: 0

list corrupt file blocks returned: 0

BLOCK* allocateBlock: /tmp/.cloudera_health_monitoring_canary_files/.canary_file_2014_10_09-07_29_47. BP-941526827-192.168.0.1-1412692043930 blk_1073744503_3679{blockUCState=UNDER_CONSTRUCTION, primaryNodeIndex=-1, replicas=[ReplicaUnderConstruction[[DISK]DS-a7270ad4-959d-4756-b731-83457af7c6a3:NORMAL|RBW]]}

BLOCK* addStoredBlock: blockMap updated: 192.168.0.102:50010 is added to blk_1073744503_3679{blockUCState=UNDER_CONSTRUCTION, primaryNodeIndex=-1, replicas=[ReplicaUnderConstruction[[DISK]DS-eaca52a9-2713-4901-b978-e331c17800fc:NORMAL|RBW]]} size 0

DIR* completeFile: /tmp/.cloudera_health_monitoring_canary_files/.canary_file_2014_10_09-07_29_47 is closed by DFSClient_NONMAPREDUCE_592472068_72

BLOCK* addToInvalidates: blk_1073744503_3679 192.168.0.102:50010 

BLOCK* BlockManager: ask 192.168.0.102:50010 to delete [blk_1073744503_3679]

Rescanning after 30001 milliseconds

Scanned 0 directive(s) and 0 block(s) in 0 millisecond(s).

[#2]

No One knows?????

[#3]

You could get this error if the secondary or standby namenode is not performing checkpointing correctly. Please verify the health of the following roles:
- Standby Namenode (if HDFS-HA is enabled)
- Secondary Namenode (if HDFS-HA is *not* enabled)

[#4]

Hi

we enabled HA . we are also getting same below error, How to fix this issue

The health test result for NAME_NODE_HA_CHECKPOINT_AGE has become concerning: The filesystem checkpoint is 3 minute(s), 36 second(s) old. This is 6.00% of the configured checkpoint period of 1 hour(s). 2,046,490 transactions have occurred since the last filesystem checkpoint. This is 204.65% of the configured checkpoint transaction target of 1,000,000. Warning threshold: 200.00%.

[#5]

Any solution this

[#6]

This is what it states.

The filesystem checkpoint is 2 day(s), 59 minute(s) old. This is 4,898.53% of the configured checkpoint period of 1 hour(s). Critical threshold: 400.00%. 23,261 transactions have occurred since the last filesystem checkpoint. This is 2.33% of the configured checkpoint transaction target of 1,000,000.

[#7]

It seems like HA settings are enabled.

Please check if HDFS>Configuration>"Filesystem Checkpoint Age Monitoring Thresholds"  is specified.  If specified then change it to never as shown below. Save the settings you will not get the message again.

[#8]

Please never disable that check. Checkpoints are very essential for the HDFS operation, and you do not want to be in a position with checkpoints failing for a technical reason and you never getting notified on that.

Instead, look at your Standby or Secondary NN to figure out what the error is, and/or seek help with that identified information.

[#9 · Accepted solution]

I found the fix for my issue.

As after format of namenode, checkpointing on snn was not happening bcoz of old namespace and blockpoolID on VERSION file.

After deleting the files under /data/dfs/snn. I restart the namenode and snn, later found it working fine.

[#10]

what is it the files under snn ?

: )