[
https://issues.apache.org/jira/browse/HBASE-10624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916272#comment-13916272
]
Lars Hofhansl commented on HBASE-10624:
---------------------------------------
Hmm... I'd be happier if we had synchronized writers and the members involved
declared volatile.
The atomics are at least as expensive as a volatile.
> Fix 2 new findbugs warnings
> ---------------------------
>
> Key: HBASE-10624
> URL: https://issues.apache.org/jira/browse/HBASE-10624
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Attachments: 10624-v1.txt, 10624-v2.txt, 10624-v4.txt
>
>
> Inconsistent synchronization of
> org.apache.hadoop.hbase.regionserver.TimeRangeTracker.maximumTimestamp;
> locked 66% of time
> {code}
> In class org.apache.hadoop.hbase.regionserver.TimeRangeTracker
> Field org.apache.hadoop.hbase.regionserver.TimeRangeTracker.maximumTimestamp
> Synchronized 66% of the time
> {code}
> Inconsistent synchronization of
> org.apache.hadoop.hbase.regionserver.TimeRangeTracker.minimumTimestamp;
> locked 62% of time
> {code}
> In class org.apache.hadoop.hbase.regionserver.TimeRangeTracker
> Field org.apache.hadoop.hbase.regionserver.TimeRangeTracker.minimumTimestamp
> Synchronized 62% of the time
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
