hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-3709) Lock hierarchy violation in namenode while handling hearbeats
Date Fri, 01 Aug 2008 07:50:33 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

dhruba borthakur resolved HADOOP-3709.

    Resolution: Invalid

This was an invalid issue.

> Lock hierarchy violation in namenode while handling hearbeats
> -------------------------------------------------------------
>                 Key: HADOOP-3709
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3709
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
> The heartbeat processing code recently got rearranged via HADOOP-3254. FSNamesystem.handleHeartbeat
acquires the hearbeat lock and then invoke blockReportProcessed. This method tries to acquire
the global FSNamesystem lock. This is a lock hierarchy violation. This leads to deadlock.
> The heatbeat processing code should acquire only the heartbeat lock. It should not acquire
the global lock, otherwise heartprocessing become too heavyweight.
> This code occurs only on trunk and not o 018 branch. Surprise!

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message