[
https://issues.apache.org/jira/browse/HBASE-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849029#action_12849029
]
Todd Lipcon commented on HBASE-2332:
------------------------------------
Another idea here suggested by a coworker of mine is to make row locks
advisory, similar to flock(2). These locks would be entirely decoupled from the
internal row locks used by HBase - that is to say, they wouldn't block other
clients from doing mutations, unless the other clients were also taking locks
on these rows.
We could even offer shared/exclusive locks if we wanted to get fancy here :)
> Remove client-exposed row locks from region server
> --------------------------------------------------
>
> Key: HBASE-2332
> URL: https://issues.apache.org/jira/browse/HBASE-2332
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: client, regionserver
> Reporter: Todd Lipcon
> Fix For: 0.21.0
>
>
> Discussion in HBASE-2294 has surfaced that the client-exposed row lock
> feature in the HBase API may not be scalable/necessary. Additionally there
> are some benefits we can reap by removing the feature (or pushing it into the
> client).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
