You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/07/05 00:48:21 UTC
[jira] [Resolved] (HDFS-2123) 1073: Checkpoint interval should be
based on txn count, not size
[ https://issues.apache.org/jira/browse/HDFS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon resolved HDFS-2123.
-------------------------------
Resolution: Fixed
Release Note: The SecondaryNameNode and CheckpointNode no longer respect the value of 'dfs.namenode.checkpoint.size' (formerly known as 'fs.checkpoint.size' in 0.20 and before). Instead, use the new configuration 'dfs.namenode.checkpoint.txns' to specify the number of transactions after which the checkpointer will trigger a new checkpoint.
Hadoop Flags: [Incompatible change, Reviewed]
> 1073: Checkpoint interval should be based on txn count, not size
> ----------------------------------------------------------------
>
> Key: HDFS-2123
> URL: https://issues.apache.org/jira/browse/HDFS-2123
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: name-node
> Affects Versions: Edit log branch (HDFS-1073)
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: Edit log branch (HDFS-1073)
>
> Attachments: hdfs-2123.txt, hdfs-2123.txt
>
>
> Currently, the administrator can configure the secondary namenode to checkpoint either every N seconds, or every N bytes worth of edit log. It would make more sense to get rid of the size-based interval and instead allow the administrator to specify checkpoints every N transactions. This also simplifies the code a little bit.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira