[
https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12148:
--------------------------
Attachment: HBASE-12148.branch-1.v5.patch
Another version of the patch that lets min and max run independent of each
other using atomiclongs and CAS instead of synchronizes.
Need this because even though doing pure read load at the moment, the memstore
uses the includesTimeRange test when its checking Gets to return. Will post
image in a sec.
> Remove TimeRangeTracker as point of contention when many threads writing a
> Store
> --------------------------------------------------------------------------------
>
> Key: HBASE-12148
> URL: https://issues.apache.org/jira/browse/HBASE-12148
> Project: HBase
> Issue Type: Sub-task
> Components: Performance
> Affects Versions: 2.0.0, 0.99.1
> Reporter: stack
> Assignee: Walter Koetke
> Fix For: 2.0.0, 1.3.0, 0.98.19
>
> Attachments:
> 0001-In-AtomicUtils-change-updateMin-and-updateMax-to-ret.patch,
> 12148.addendum.txt, 12148.min_and_max_run_independent.patch, 12148.txt,
> 12148.txt, 12148v2.txt, 12148v2.txt, 12148v4.patch, HBASE-12148-V3.patch,
> HBASE-12148-V3.patch, HBASE-12148.branch-1.v5.patch, HBASE-12148.txt,
> HBASE-12148V2.txt, Screen Shot 2014-10-01 at 3.39.46 PM.png, Screen Shot
> 2014-10-01 at 3.41.07 PM.png, Screen Shot 2016-04-13 at 1.49.30 PM.png,
> Screen Shot 2016-04-13 at 2.02.22 PM.png, TimeRangeTracker.tiff
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
