hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5311) Write pipeline recovery fails
Date Mon, 23 Feb 2009 23:54:02 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676132#action_12676132

Tsz Wo (Nicholas), SZE commented on HADOOP-5311:

> One side issue... DFSClient and NameNode used a different node as a primary datanode
for pipeline recovery of the same block. That was why I did not see NameNode-initiated pipeline
recovery at first. Will this cause the deadlock reported HADOOP-3673?

One of the necessary conditions for a deadlock is hold-and-wait.  In NameNode initiated recovery,
NameNode use the so called reverse-heartbeat to send the recovery command, which does not
hold Datanode RPC thread.  The hold-and-wait condition cannot be satisfied.

> Write pipeline recovery fails
> -----------------------------
>                 Key: HADOOP-5311
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5311
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.0
>            Reporter: Hairong Kuang
>             Fix For: 0.18.4
> A write pipeline recovery fails on the error below:
> INFO org.apache.hadoop.ipc.Server: IPC Server handler 2 on 53006, call recoverBlock(blk_1415000632081498137_954380,
false, [Lorg.apache.hadoop.hdfs.protocol.DatanodeInfo;
> @4ec82dc6) from XX: error: org.apache.hadoop.ipc.RemoteException: java.io.IOException:
blk_1415000632081498137_954380 is already commited, storedBlock == null.
>         at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.nextGenerationStampForBlock(FSNamesystem.java:4487)
>         at org.apache.hadoop.hdfs.server.namenode.NameNode.nextGenerationStamp(NameNode.java:473)
>         at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:508)
>         at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:959)
>         at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:955)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at javax.security.auth.Subject.doAs(Subject.java:396)
>         at org.apache.hadoop.ipc.Server$Handler.run(Server.java:953)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message