[
https://issues.apache.org/jira/browse/HBASE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HBASE-2295:
------------------------------------
Attachment: rowLockDeadlock.txt
1. Changed locksToRows to be a Set (instead of a Map)
2. Generate sequential lockids, and in the case of collision use a Random
number to start from a new origin
> 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
>
>
> 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.
