Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Thu, 8 Dec 2011 23:57:40 +0000 (UTC)
From: "Todd Lipcon (Resolved) (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: 
 <941124817.55672.1323388660245.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <306267105.43092.1323126400311.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (HDFS-2634) Standby needs to ingest latest edit
 logs before transitioning to active`
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon resolved HDFS-2634.
-------------------------------

       Resolution: Fixed
    Fix Version/s: HA branch (HDFS-1623)
     Hadoop Flags: Reviewed

committed latest patch, thx for the reviews.
                
> Standby needs to ingest latest edit logs before transitioning to active`
> ------------------------------------------------------------------------
>
>                 Key: HDFS-2634
>                 URL: https://issues.apache.org/jira/browse/HDFS-2634
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: HA branch (HDFS-1623)
>
>         Attachments: hdfs-2634.txt, hdfs-2634.txt
>
>
> When the standby transitions to active state, it needs to _read_ the latest edit logs before it reopens them for write access. Currently, the transition calls {{stopStandbyServices}}, which stops the tailer, but doesn't read ahead to the very end. This ends up leaving the shared edits dir in an inconsistent state where we have overlapping transaction IDs.

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