[
https://issues.apache.org/jira/browse/HBASE-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159823#comment-15159823
]
Sean Busbey commented on HBASE-15222:
-------------------------------------
Alternatively, we could waste a bunch of energy on getting a manual ordering of
our modules in place, as was required prior to YETUS-280. that would allow us
to get the correct behavior with the current release.
Personally, I don't think it's worth it given how un-often we run into this
problem. I'll start a Yetus release vote on Friday and on Monday we'll switch
to new release that contains the fix.
> Use less contended classes for metrics
> --------------------------------------
>
> Key: HBASE-15222
> URL: https://issues.apache.org/jira/browse/HBASE-15222
> Project: HBase
> Issue Type: Bug
> Components: metrics
> Affects Versions: 2.0.0, 1.2.0, 1.3.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Priority: Critical
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-15222-v1.patch, HBASE-15222-v10.patch,
> HBASE-15222-v11.patch, HBASE-15222-v12.patch, HBASE-15222-v13.patch,
> HBASE-15222-v2.patch, HBASE-15222-v3.patch, HBASE-15222-v5.patch,
> HBASE-15222-v6.patch, HBASE-15222-v8.patch, HBASE-15222-v9.patch,
> HBASE-15222.patch
>
>
> Running the benchmarks now, but it looks like the results are pretty extreme.
> The locking in our histograms is pretty extreme.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
