hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Kunz (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4517) unstable dfs when running jobs on 0.18.1
Date Mon, 27 Oct 2008 19:01:15 GMT

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

Christian Kunz commented on HADOOP-4517:
----------------------------------------

Sorry about the late response.

As a matter of fact, before the patch was available (although it was done very fast, thank
you, Nicholas), the 3rd attempt was successful because I restarted DataNodes periodically.
Our batch of jobs continued without the patch with no problem, indicating that the dead-lock
situation is not easily reproducible. It seems to require a much higher number of simultaneous
writing clients than Datanode servers.
The specific job doing this kind of intensive writing will be re-executed in about 3 days.
Then I will try out the patch. Can you wait so long?

> 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
>            Assignee: Tsz Wo (Nicholas), SZE
>            Priority: Blocker
>             Fix For: 0.18.2, 0.19.1, 0.20.0
>
>         Attachments: 4517_20081024.patch, 4517_20081024b_0.18.patch, 4517_20081024c_0.18.patch,
4517_20081024d.patch, 4517_20081024d_0.18.patch, 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