hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2085) 1073: finalize inprogress edit logs at startup
Date Tue, 21 Jun 2011 17:07:47 GMT

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

Eli Collins commented on HDFS-2085:

Why doesn't finalizeLog need to endCurrentLogSegment? Isn't there a test that asserts all
finalized logs end with OP_END_LOG_SEGMENT?

> 1073: finalize inprogress edit logs at startup
> ----------------------------------------------
>                 Key: HDFS-2085
>                 URL: https://issues.apache.org/jira/browse/HDFS-2085
>             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-2085.txt
> With HDFS-2074, the NameNode can read through any "in-progress" logs it finds during
startup to determine how many transactions they have. It can then re-name the file from its
inprogress name to its finalized name. For example, if it finds a file edits_10_inprogress
with 3 transactions, it can rename it to edits_10-12 at startup. This means that other parts
of the system like edits-log-transfer don't need to worry about in-progress logs.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message