[
https://issues.apache.org/jira/browse/HADOOP-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642976#action_12642976
]
Raghu Angadi commented on HADOOP-4517:
--------------------------------------
Looks good. Couple of rename suggestions :
- {{ getOngoingCreatesOrUpdateBlock()}} could be called {{tryUpdateBlock()}}. I
think JavaDoc should be better.
- {{findAndUpdatedBlock()}} could be folded in to {{tryUpdateBlock()}}.
I think it will be better to get a confirmation from Christian's load before
committing it.. or at least before 0.18.2 is released.
> 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.
