[
https://issues.apache.org/jira/browse/HBASE-12148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160403#comment-14160403
]
Andrew Purtell commented on HBASE-12148:
----------------------------------------
bq. On 32bit systems an update to long is not atomic in Java, so a reader here
might see a partially updated long.
I almost feel we should doc this and move on, if anyone is running the server
side on a 32 bit JVM they shouldn't. But yeah the potential for torn reads
isn't good.
bq. I think you cannot get around declaring minimumTimestamp and
maximumTimestamp volatile, that will add some of the overhead back in.
We can make that change
> 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.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)
