[HADOOP-7117] Move secondary namenode checkpoint configs from core-default.xml to hdfs-default.xml

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.21.1, 0.22.0, 0.23.0
• Component/s: conf
• Hadoop Flags: Reviewed
• Release Note: Removed references to the older fs.checkpoint.* properties that resided in core-site.xml
• Tags: secondarynamenode, checkpoint
• Assignee: Harsh J
• Reporter: Patrick Angeles
• Created: 25/Jan/11 17:48
• Updated: 15/Nov/11 00:50
• Resolved: 16/Mar/11 22:44

Description

The following configs are in core-default.xml, but are really read by the Secondary Namenode. These should be moved to hdfs-default.xml for consistency.
<property>
<name>fs.checkpoint.dir</name>
<value>${hadoop.tmp.dir}/dfs/namesecondary</value>
<description>Determines where on the local filesystem the DFS secondary
name node should store the temporary images to merge.
If this is a comma-delimited list of directories then the image is
replicated in all of the directories for redundancy.
</description>
</property>

<property>
<name>fs.checkpoint.edits.dir</name>
<value>${fs.checkpoint.dir}</value>
<description>Determines where on the local filesystem the DFS secondary
name node should store the temporary edits to merge.
If this is a comma-delimited list of directoires then teh edits is
replicated in all of the directoires for redundancy.
Default value is same as fs.checkpoint.dir
</description>
</property>

<property>
<name>fs.checkpoint.period</name>
<value>3600</value>
<description>The number of seconds between two periodic checkpoints.
</description>
</property>

<property>
<name>fs.checkpoint.size</name>
<value>67108864</value>
<description>The size of the current edit log (in bytes) that triggers
a periodic checkpoint even if the fs.checkpoint.period hasn't expired.
</description>
</property>

Issue Links

• is related to: HDFS-1596 Move secondary namenode checkpoint configs from core-default.xml to hdfs-default.xml