Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 27 May 2011 20:44:47 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1915593855.49777.1306529087624.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1601286575.41154.1306286327499.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-1994) Fix race conditions when running two
 rapidly checkpointing 2NNs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon resolved HDFS-1994.
-------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Fixed the nits and committed to branch.

Unfortunately Mockito doesn't provide that Answer implementation, but I based that implementation on a suggestion I found on the Mockito bugtracker.

> Fix race conditions when running two rapidly checkpointing 2NNs
> ---------------------------------------------------------------
>
>                 Key: HDFS-1994
>                 URL: https://issues.apache.org/jira/browse/HDFS-1994
>             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-1994.txt, hdfs-1994.txt
>
>
> HDFS-1984 added the ability to run two secondary namenodes at the same time. However, there were two races I found when stress testing this (by running two NNs each checkpointing in a tight loop with no sleep):
> 1) the writing of the seen_txid file was not atomic, so it was at some points reading an empty file
> 2) it was possible for two checkpointers to try to take a checkpoint at the same transaction ID, which would cause the two image downloads to collide and fail

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