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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2009/12/29 18:06:29 UTC

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

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
             Fix For: 0.22.0
         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HDFS-863:
-----------------------------

    Attachment: cycle.png

> 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
>             Fix For: 0.22.0
>
>         Attachments: 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.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HDFS-863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated HDFS-863:
-----------------------------

    Attachment: TestNodeCount.png

Same thing occurs in TestNodeCount

> 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
>             Fix For: 0.22.0
>
>         Attachments: cycle.png, TestNodeCount.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.
-
You can reply to this email to add a comment to the issue online.