[
https://issues.apache.org/jira/browse/HBASE-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033286#comment-16033286
]
Dave Latham commented on HBASE-18144:
-------------------------------------
Fascinating. Thanks, for sharing so much of the detail of the sleuthing story.
Having exclusive locks as a config option sounds like it would this one
application that is aware of what is going on, but how likely is it that other
folks are going to know when to turn this on? Would sure be great if there was
a solution that worked without configuration.
> Forward-port the old exclusive row lock; there are scenarios where it
> performs better
> -------------------------------------------------------------------------------------
>
> Key: HBASE-18144
> URL: https://issues.apache.org/jira/browse/HBASE-18144
> Project: HBase
> Issue Type: Bug
> Components: Increment
> Affects Versions: 1.2.5
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.3.2, 1.2.7
>
>
> Description to follow.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
