[
https://issues.apache.org/jira/browse/HBASE-18144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052687#comment-16052687
]
Anoop Sam John commented on HBASE-18144:
----------------------------------------
Am noticing this change now only. Am checking master code. Ya previously the
boolean param was deciding whether we should wait for the lock or not. That
was true for the 1st row in the batch and false otherwise. (As Allan explained
above).. We do the mutations in mini batches. Now seems we dont have this
boolean param based decision at all.. Any idea which issue changed this way?
[~carp84]. Thanks for the nice explanation Allan.
> 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
>
> Attachments: DisorderedBatchAndIncrementUT.patch,
> HBASE-18144.master.001.patch
>
>
> Description to follow.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
