[
https://issues.apache.org/jira/browse/HBASE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842839#action_12842839
]
stack commented on HBASE-2295:
------------------------------
@Dhruba
If you want to use a SortedSet and pass a comparator instead, so you can retain
byte [] elements, there is a bytes comparator here:
http://hadoop.apache.org/hbase/docs/r0.20.3/api/org/apache/hadoop/hbase/util/Bytes.html#BYTES_COMPARATOR
Otherwise, patch looks good.
Regards TRUNK, its been mavenized so to build it, you need maven -- see
http://wiki.apache.org/hadoop/Hbase/MavenPrimer -- and then to build and run
tests do something like mvn install
> 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.
