hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-863) Potential deadlock in TestOverReplicatedBlocks
Date Mon, 24 Jan 2011 19:44:46 GMT

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

Todd Lipcon commented on HDFS-863:

Seems the new writeUnlock() calls should be inside a finally{} clause, no? Otherwise I fear
we might get a test timeout if one of these functions throws an exception (since the minicluster
wouldn't be able to shutdown if the writelock is left held)

> 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: cycle.png, HDFS-863.patch, 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.

View raw message