You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/04/21 01:33:37 UTC

[jira] [Commented] (HDFS-863) Potential deadlock in TestOverReplicatedBlocks

    [ https://issues.apache.org/jira/browse/HDFS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022535#comment-13022535 ] 

Hudson commented on HDFS-863:
-----------------------------

Integrated in Hadoop-Hdfs-trunk #643 (See [https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/643/])
    

> Potential deadlock in TestOverReplicatedBlocks
> ----------------------------------------------
>
>                 Key: HDFS-863
>                 URL: https://issues.apache.org/jira/browse/HDFS-863
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>            Reporter: Todd Lipcon
>            Assignee: Ken Goodhope
>             Fix For: 0.23.0
>
>         Attachments: HDFS-863.patch, HDFS-863.patch, HDFS-863.patch, HDFS-863.patch, TestNodeCount.png, cycle.png
>
>
> TestOverReplicatedBlocks.testProcesOverReplicateBlock synchronizes on namesystem.heartbeats without synchronizing on namesystem first. Other places in the code synchronize namesystem, then heartbeats. It's probably unlikely to occur in this test case, but it's a simple fix.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira