Return-Path: 
 <hdfs-issues-return-33207-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BDB3A955E
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Wed,  1 Feb 2012 01:49:18 +0000 (UTC)
Received: (qmail 17872 invoked by uid 500); 1 Feb 2012 01:49:18 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 17844 invoked by uid 500); 1 Feb 2012 01:49:17 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 17836 invoked by uid 99); 1 Feb 2012 01:49:17 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2012 01:49:17 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Feb 2012 01:49:16 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id B4C5416770C
	for <hdfs-issues@hadoop.apache.org>; Wed,  1 Feb 2012 01:48:56 +0000 (UTC)
Date: Wed, 1 Feb 2012 01:48:56 +0000 (UTC)
From: "Hari Mankude (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1016947520.1042.1328060936741.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <70979041.12836.1328040251142.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2866) Standby does not start up due to a
 gap in transaction id
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Hari Mankude commented on HDFS-2866:
------------------------------------

@Aaron,

name.dir and shared.edits.dir are nfs mounted.  Regarding second question, the logs are from the newly active NN. The newly active NN just took over from the previous NN which was killed. I have highlighted the logs from transitiontoActive.

     <property>
         <name>dfs.name.dir</name>
         <value>/homes/hortonha/namenode/fsimage</value>
     </property>
     <property>
         <name>dfs.namenode.shared.edits.dir</name>
         <value>/homes/hortonha/namenode</value>
     </property>

                
> Standby does not start up due to a gap in transaction id
> --------------------------------------------------------
>
>                 Key: HDFS-2866
>                 URL: https://issues.apache.org/jira/browse/HDFS-2866
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Hari Mankude
>            Priority: Critical
>
> Standby notices a gap in the transaction id in the shared.edits directory. The transactions in dfs.edits.dir does not seem to have the gap. The gap happens during a failover.

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