hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2123) 1073: Checkpoint interval should be based on txn count, not size
Date Mon, 04 Jul 2011 22:33:22 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059629#comment-13059629

Todd Lipcon commented on HDFS-2123:

hmm.. I added it as a deprecated key, but I think it's now going to have the wrong effect
- ie it will treat the byte value as a number of transactions. Instead, it's probably better
to emit a warning and ignore. Let me update the patch.

> 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
> 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


View raw message