Return-Path: 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 E3C8AF689 for ; Tue, 9 Jul 2013 03:39:51 +0000 (UTC) Received: (qmail 32795 invoked by uid 500); 9 Jul 2013 03:39:51 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 32610 invoked by uid 500); 9 Jul 2013 03:39:50 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 32431 invoked by uid 99); 9 Jul 2013 03:39:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jul 2013 03:39:49 +0000 Date: Tue, 9 Jul 2013 03:39:49 +0000 (UTC) From: "Fengdong Yu (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-4967) Generate block ID sequentially cannot work with QJM HA 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-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fengdong Yu updated HDFS-4967: ------------------------------ Description: There are two name nodes, one is active, another acts as standby name node. QJM Ha configured. After HDFS-4645 committed in the trunk, then the following error showed during name node start: {code} 2013-07-09 11:28:45,394 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join java.lang.IllegalStateException: Cannot skip to less than the current value (=1073741824), where newValue=0 at org.apache.hadoop.util.SequentialNumber.skipTo(SequentialNumber.java:58) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.setLastAllocatedBlockId(FSNamesystem.java:5124) at org.apache.hadoop.hdfs.server.namenode.FSImageFormat$Loader.load(FSImageFormat.java:278) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:809) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:798) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:653) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:623) at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:260) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:719) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:552) at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:401) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:435) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:607) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:592) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1172) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1238) 2013-07-09 11:28:45,397 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 1 {code} was: After HDFS-4645 committed in the trunk, then the following error showed during name node start: {code} 2013-07-09 11:28:45,394 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join java.lang.IllegalStateException: Cannot skip to less than the current value (=1073741824), where newValue=0 at org.apache.hadoop.util.SequentialNumber.skipTo(SequentialNumber.java:58) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.setLastAllocatedBlockId(FSNamesystem.java:5124) at org.apache.hadoop.hdfs.server.namenode.FSImageFormat$Loader.load(FSImageFormat.java:278) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:809) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:798) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:653) at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:623) at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:260) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:719) at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:552) at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:401) at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:435) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:607) at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:592) at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1172) at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1238) 2013-07-09 11:28:45,397 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 1 {code} There are two name nodes, one is active, another acts as standby name node. QJM Ha configured. > Generate block ID sequentially cannot work with QJM HA > ------------------------------------------------------ > > Key: HDFS-4967 > URL: https://issues.apache.org/jira/browse/HDFS-4967 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, hdfs-client, namenode > Affects Versions: 3.0.0 > Reporter: Fengdong Yu > > There are two name nodes, one is active, another acts as standby name node. QJM Ha configured. > After HDFS-4645 committed in the trunk, then the following error showed during name node start: > {code} > 2013-07-09 11:28:45,394 FATAL org.apache.hadoop.hdfs.server.namenode.NameNode: Exception in namenode join > java.lang.IllegalStateException: Cannot skip to less than the current value (=1073741824), where newValue=0 > at org.apache.hadoop.util.SequentialNumber.skipTo(SequentialNumber.java:58) > at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.setLastAllocatedBlockId(FSNamesystem.java:5124) > at org.apache.hadoop.hdfs.server.namenode.FSImageFormat$Loader.load(FSImageFormat.java:278) > at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:809) > at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:798) > at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImageFile(FSImage.java:653) > at org.apache.hadoop.hdfs.server.namenode.FSImage.loadFSImage(FSImage.java:623) > at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:260) > at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:719) > at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:552) > at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:401) > at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:435) > at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:607) > at org.apache.hadoop.hdfs.server.namenode.NameNode.(NameNode.java:592) > at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1172) > at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1238) > 2013-07-09 11:28:45,397 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 1 > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira