[
https://issues.apache.org/jira/browse/HBASE-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849059#action_12849059
]
Jean-Daniel Cryans commented on HBASE-2332:
-------------------------------------------
bq. they wouldn't block other clients from doing mutations, unless the other
clients were also taking locks on these rows.
That's what I had in mind when I commented on HBASE-2294:
bq. <crazyidea>If we remove row locks from core HBase, maybe we should still
support them at the HTable level but by using ZK directly instead of contacting
region servers.</crazyidea>
So it would be strictly between the clients and a coordinator like zookeeper,
not involving the RS side at all.
> 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.
