[
https://issues.apache.org/jira/browse/HADOOP-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639867#action_12639867
]
Sameer Paranjpye commented on HADOOP-4278:
------------------------------------------
> It is likely to be a problem with the test. In real-life, if a datanode in
> the oipleine dies, it is very likely that all the threads in that Datanode
> become
> inactive, so it will not matter whether the block-receiver thread or the
> packer responder thread exited first.
The client should be able to do a better job of detecting which Datanode died,
no? The current implementation means that if a Datanode in a write pipeline
dies the writer wil frequently fail. Datanode death is not a very frequent
event so this is likely not a blocker, but I'd say that our test is triggering
a known issue rather than saying it has a bug.
> TestDatanodeDeath failed occasionally
> -------------------------------------
>
> Key: HADOOP-4278
> URL: https://issues.apache.org/jira/browse/HADOOP-4278
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: dhruba borthakur
> Priority: Blocker
> Fix For: 0.19.0
>
>
> TestDatanodeDeath keeps failing occasionally. For example, see
> http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3365/testReport/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
