hbase-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: (HBASE-2295) Row locks may deadlock with themselves
Date Tue, 09 Mar 2010 18:27:27 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843219#action_12843219
] 

Todd Lipcon commented on HBASE-2295:
------------------------------------

This already went in, but one quick note on the final patch: rather than checking locksToRows.size()
> 0, it's probably faster to check !locksToRows.isEmpty()

Does this need to be a followup JIRA?

> 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
>            Assignee: dhruba borthakur
>             Fix For: 0.20.4, 0.21.0
>
>         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.


Mime
View raw message