[
https://issues.apache.org/jira/browse/HBASE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842490#action_12842490
]
ryan rawson commented on HBASE-2295:
------------------------------------
The multiput does not promise nor do multi row atomic puts. It actually just
calls the array put API.
On Mar 7, 2010 11:11 AM, "dhruba borthakur (JIRA)" <[email protected]> wrote:
[
https://issues.apache.org/jira/browse/HBASE-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842465#action_12842465]
dhruba borthakur commented on HBASE-2295:
-----------------------------------------
are you talking about the multiPut where multiple rows could be updated
atomically by an app?
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.
> 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
>
> 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.
