Move secondary namenode checkpoint configs from core-default.xml to
hdfs-default.xml
------------------------------------------------------------------------------------
Key: HADOOP-7117
URL: https://issues.apache.org/jira/browse/HADOOP-7117
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Reporter: Patrick Angeles
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>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
