How to control the occurrence frequency of namenode checkpoints

How to control the occurrence frequency of namenode checkpoints

The secondarynamenode node regularly accesses namenode to back up image files and edit logs. How can this frequency be modified?

This experiment is based on the experiment of separating namenode and secondarynamenode in Hadoop0.20.2 (see). Therefore, this article provides a proof of the correct effect after the separation.

Modify the core-site.xml file fs. checkpoint. period configuration parameter for the secondarynamenode node, which was originally 3600 (that is, 1 hour) and now changes to 120 (two minutes ).

Restart the cluster after saving or separately start the secondarynamenode node.

Go to fs. checkpoint. the directory secondaryname set by dir shows the current and other directories and files (proving that the experiment in this article "separation of namenode and secondarynamenode Based on hadoop0.20.2" is successful)

In addition, we can see that the Directory Creation Time changes every two minutes, for example:

This indicates that the checkpoint frequency of the secondarynamenode node has been modified successfully.

Tutorial on standalone/pseudo-distributed installation and configuration of Hadoop2.4.1 under Ubuntu14.04

Install and configure Hadoop2.2.0 on CentOS

Build a Hadoop environment on Ubuntu 13.04

Cluster configuration for Ubuntu 12.10 + Hadoop 1.2.1

Build a Hadoop environment on Ubuntu (standalone mode + pseudo Distribution Mode)

Configuration of Hadoop environment in Ubuntu

Detailed tutorial on creating a Hadoop environment for standalone Edition

Build a Hadoop environment (using virtual machines to build two Ubuntu systems in a Winodws environment)