Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6855EFFC8 for ; Thu, 11 Apr 2013 02:59:17 +0000 (UTC) Received: (qmail 15176 invoked by uid 500); 11 Apr 2013 02:59:16 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 15086 invoked by uid 500); 11 Apr 2013 02:59:16 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 14814 invoked by uid 99); 11 Apr 2013 02:59:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Apr 2013 02:59:16 +0000 Date: Thu, 11 Apr 2013 02:59:15 +0000 (UTC) From: "Brandon Li (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (HDFS-4654) FileNotFoundException: ID mismatch 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-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li resolved HDFS-4654. ------------------------------ Resolution: Not A Problem Assignee: Brandon Li Given HDFS-4339 has been committed. This JIRA is not a problem any more. > FileNotFoundException: ID mismatch > ---------------------------------- > > Key: HDFS-4654 > URL: https://issues.apache.org/jira/browse/HDFS-4654 > Project: Hadoop HDFS > Issue Type: Bug > Components: ha, namenode > Affects Versions: 3.0.0 > Reporter: Fengdong Yu > Assignee: Brandon Li > Fix For: 3.0.0 > > > Mu cluster was build from source code trunk r1463074. > I got an exception as follows when I put a file to the HDFS. > 13/04/01 09:33:45 WARN retry.RetryInvocationHandler: Exception while invoking addBlock of class ClientNamenodeProtocolTranslatorPB. Trying to fail over immediately. > 13/04/01 09:33:45 WARN hdfs.DFSClient: DataStreamer Exception > java.io.FileNotFoundException: ID mismatch. Request id and saved id: 1073 , 1050 > at org.apache.hadoop.hdfs.server.namenode.INodeId.checkId(INodeId.java:51) > at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkLease(FSNamesystem.java:2501) > at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.analyzeFileState(FSNamesystem.java:2298) > at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getAdditionalBlock(FSNamesystem.java:2212) > at org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.addBlock(NameNodeRpcServer.java:498) > at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.addBlock(ClientNamenodeProtocolServerSideTranslatorPB.java:356) > at org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java:40979) > at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:526) > at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1018) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1818) > at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1814) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1489) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1812) > please reproduce as : > hdfs dfs -put test.data /user/data/test.data > after this command start to run, then kill active name node process. > I have only three nodes(A,B,C) for test > A and B are name nodes. > B and C are data nodes. > ZK deployed on A, B and C. > A, B and C are all journal nodes. > Thanks. -- 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