hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12148) Remove TimeRangeTracker as point of contention when many threads writing a Store
Date Mon, 06 Oct 2014 22:40:34 GMT

    [ https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161147#comment-14161147
] 

stack commented on HBASE-12148:
-------------------------------

Did atomic/volatile because of above pushback that no guarantee that long update is atomic
-- which would mess up any compare. You thinking I've almost put back the synchronized block
since the reads are of volatiles/AtomicLong [~mbertozzi]?  The sync scope is narrowed some
at least.  I didn't measure in context.  If any question at all, I'll just put back old behavior
until I get chance to test in context again.

> 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: stack
>             Fix For: 2.0.0, 0.98.7, 0.99.1
>
>         Attachments: 12148.addendum.txt, 12148.txt, 12148.txt, 12148v2.txt, 12148v2.txt,
Screen Shot 2014-10-01 at 3.39.46 PM.png, Screen Shot 2014-10-01 at 3.41.07 PM.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message