[
https://issues.apache.org/jira/browse/HBASE-15650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363606#comment-15363606
]
Andrew Purtell edited comment on HBASE-15650 at 7/6/16 1:56 AM:
----------------------------------------------------------------
bq. do you regularly run ITBLL on a sizable cluster with 0.98 which has this
optimization in? If you do and you never saw any lost refs
[~mantonov] No I do not run ITBLL on a sizable cluster for 0.98. Question of
access to resources. Looking to change that with something DIY on EC2 with
[~dimaspivak]'s clusterdock stuff. Will look for this problem on 0.98.
was (Author: apurtell):
bq. do you regularly run ITBLL on a sizable cluster with 0.98 which has this
optimization in? If you do and you never saw any lost refs
[~mantonov] No I do not run ITBLL on a sizable cluster for 0.98. Question of
access to resources. Looking to change that with something DIY on EC2 with
[~dimaspivak]'s clusterdock stuff.
> 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, 1.3.0, 0.98.19, 1.4.0
>
> Attachments: 15650.branch-1.2.patch, 15650.branch-1.patch,
> 15650.branch-1.patch, 15650.patch, 15650.patch, 15650v2.branch-1.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)
