hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4517) unstable dfs when running jobs on 0.18.1
Date Fri, 24 Oct 2008 20:41:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642538#action_12642538
] 

Raghu Angadi commented on HADOOP-4517:
--------------------------------------

Seems like a deadlock in Datanode. This essentially freezes the datanode and eventually it
will marked dead. 

The deadlock is between the threads {{nid=0xf05}} (A) and {{nid=0x6a81}} (B). B is waiting
for A to exit, but A is trying to acquire a lock held by B. It seems to be new append related
code in 0.18. I don't think the exceptions are related.

- A : {noformat} "org.apache.hadoop.dfs.DataNode$DataXceiver@1ccd900" daemon prio=10 tid=0x09368000
nid=0xf05 waiting for monitor entry [0x9bb21000..0x9bb21ea0]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.apache.hadoop.dfs.FSDataset.setChannelPosition(FSDataset.java:977)
	- waiting to lock <0xb64e9c20> (a org.apache.hadoop.dfs.FSDataset)
	at org.apache.hadoop.dfs.DataNode$BlockReceiver.setBlockPosition(DataNode.java:2791)
	at org.apache.hadoop.dfs.DataNode$BlockReceiver.receivePacket(DataNode.java:2596)
	at org.apache.hadoop.dfs.DataNode$BlockReceiver.receiveBlock(DataNode.java:2698)
	at org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1283)
	at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:1045)
	at java.lang.Thread.run(Thread.java:619)
{noformat}

- B : {noformat}"org.apache.hadoop.dfs.DataNode$DataXceiver@1ccd900" daemon prio=10 tid=0x09368000
nid=0xf05 waiting for monitor entry [0x9bb21000..0x9bb21ea0]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.apache.hadoop.dfs.FSDataset.setChannelPosition(FSDataset.java:977)
	- waiting to lock <0xb64e9c20> (a org.apache.hadoop.dfs.FSDataset)
	at org.apache.hadoop.dfs.DataNode$BlockReceiver.setBlockPosition(DataNode.java:2791)
	at org.apache.hadoop.dfs.DataNode$BlockReceiver.receivePacket(DataNode.java:2596)
	at org.apache.hadoop.dfs.DataNode$BlockReceiver.receiveBlock(DataNode.java:2698)
	at org.apache.hadoop.dfs.DataNode$DataXceiver.writeBlock(DataNode.java:1283)
	at org.apache.hadoop.dfs.DataNode$DataXceiver.run(DataNode.java:1045)
	at java.lang.Thread.run(Thread.java:619)
{noformat}


> unstable dfs when running jobs on 0.18.1
> ----------------------------------------
>
>                 Key: HADOOP-4517
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4517
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.1
>         Environment: hadoop-0.18.1 plus patches HADOOP-4277 HADOOP-4271 HADOOP-4326 HADOOP-4314
HADOOP-3914 HADOOP-4318 HADOOP-4351 HADOOP-4395
>            Reporter: Christian Kunz
>             Fix For: 0.18.2, 0.19.1, 0.20.0
>
>         Attachments: datanode.out
>
>
> 2 attempts of a job using 6000 maps, 1900 reduces
> 1.st attempt: failed during reduce phase after 22 hours with 31 dead datanodes most of
which became unresponsive due to an exception; dfs lost blocks
> 2nd attempt: failed during map phase after 5 hours with 5 dead datanodes due to exception;
dfs lost blocks responsible for job failure.
> I will post typical datanode exception and attach thread dump.

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


Mime
View raw message