Mailing-List: contact hbase-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-issues@hadoop.apache.org
Message-ID: <905442816.150791268122887162.JavaMail.jira@brutus.apache.org>
Date: Tue, 9 Mar 2010 08:21:27 +0000 (UTC)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hbase-issues@hadoop.apache.org
Subject: [jira] Updated: (HBASE-2295) Row locks may deadlock with themselves
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

dhruba borthakur updated HBASE-2295:
------------------------------------

    Attachment: rowLockDeadlock2.txt

This patch incorporates Todd's and Stack's comments. And is for hbase trunk.

> Row locks may deadlock with themselves
> --------------------------------------
>
>                 Key: HBASE-2295
>                 URL: https://issues.apache.org/jira/browse/HBASE-2295
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Todd Lipcon
>         Attachments: rowLockDeadlock.txt, rowLockDeadlock2.txt
>
>
> Row locks in HRegion are keyed by a int-sized hash of the row key. It's perfectly possible for two rows to hash to the same key. So, if any client tries to lock both rows, it will deadlock with itself. Switching to a 64-bit hash is an improvement but still sketchy.

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