Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates
 209.85.223.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADY20s6zSe6eza4TcQD9dJj04prw9Uhts_7rvEaczTEpv1_B8g@mail.gmail.com>
References: 
 <CALr1C9pnWqTXm8vAjRj_0MzEy0aJhxwBRyGTh9dcuZdQBLgyag@mail.gmail.com>
 <CADY20s6zSe6eza4TcQD9dJj04prw9Uhts_7rvEaczTEpv1_B8g@mail.gmail.com>
From: Harsh J <harsh@cloudera.com>
Date: Mon, 1 Apr 2013 10:42:27 +0530
Message-ID: 
 <CAOcnVr1+BHU6=H3T82MLesW7=oqvDzZdNeaCZjGJ4-rd_k=Jnw@mail.gmail.com>
Subject: Re: Exception with QJM HDFS HA
To: hdfs dev <hdfs-dev@hadoop.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

A JIRA was posted by Azuryy for this at
https://issues.apache.org/jira/browse/HDFS-4654.

On Mon, Apr 1, 2013 at 10:40 AM, Todd Lipcon <todd@cloudera.com> wrote:
> This looks like a bug with the new inode ID code in trunk, rather than a
> bug with QJM or HA.
>
> Suresh/Brandon, any thoughts?
>
> -Todd
>
> On Sun, Mar 31, 2013 at 6:43 PM, Azuryy Yu <azuryyyu@gmail.com> wrote:
>
>> Hi All,
>>
>> I configured HDFS Ha using source code from 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.
>>
>
>
>
> --
> Todd Lipcon
> Software Engineer, Cloudera


-- 
Harsh J