Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Tue, 10 Jan 2012 01:15:39 +0000 (UTC)
From: "Todd Lipcon (Created) (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <1376484423.23944.1326158139770.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HDFS-2773) HA: reading edit logs from an earlier
 version leaves blocks in under-construction state
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

HA: reading edit logs from an earlier version leaves blocks in under-construction state
---------------------------------------------------------------------------------------

                 Key: HDFS-2773
                 URL: https://issues.apache.org/jira/browse/HDFS-2773
             Project: Hadoop HDFS
          Issue Type: Sub-task
          Components: ha, name-node
    Affects Versions: HA branch (HDFS-1623)
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon
            Priority: Blocker


In HDFS-2602, the code for applying OP_ADD and OP_CLOSE was changed a bit, and the new code has the following problem: if an OP_CLOSE includes new blocks (ie not previously seen in an OP_ADD) then those blocks will remain in the "under construction" state rather than being marked "complete". This is because {{updateBlocks}} always creates {{BlockInfoUnderConstruction}} regardless of the opcode. This bug only affects the upgrade path, since in trunk we always persist blocks with OP_ADDs before we call OP_CLOSE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira