Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Mon, 20 Jun 2011 18:24:47 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <280579860.21805.1308594287569.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <339306911.21796.1308594167448.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-2085) 1073: finalize inprogress edit logs at
 startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HDFS-2085:
------------------------------

          Component/s: name-node
    Affects Version/s: Edit log branch (HDFS-1073)
        Fix Version/s: Edit log branch (HDFS-1073)

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