[
https://issues.apache.org/jira/browse/HBASE-15650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15650:
--------------------------
Attachment: 15650v6.patch
Remove the TODO.
The TODO was me thinking we were 'calculating' the final state of the
TimeRangeTracker twice; once when we were writing the memstore and then again
when we were flushing the file out.
I see that this is not the case. It is cryptic but we go out of our way to
avoid doing this. I tried to make it so no one ended up having the 'same' idea
all over again with comments elsewhere in v3 or so of the patch.
This version removes the TODO.
> Remove TimeRangeTracker as point of contention when many threads reading a
> StoreFile
> ------------------------------------------------------------------------------------
>
> Key: HBASE-15650
> URL: https://issues.apache.org/jira/browse/HBASE-15650
> Project: HBase
> Issue Type: Bug
> Components: Performance
> Affects Versions: 2.0.0
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0
>
> Attachments: 15650.branch-1.patch, 15650.patch, 15650.patch,
> 15650v2.patch, 15650v3.patch, 15650v4.patch, 15650v5.patch, 15650v6.patch,
> Point-of-contention-on-random-read.png
>
>
> HBASE-12148 is about "Remove TimeRangeTracker as point of contention when
> many threads writing a Store". It is also a point of contention when reading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
