[
https://issues.apache.org/jira/browse/HBASE-15222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159819#comment-15159819
]
Sean Busbey commented on HBASE-15222:
-------------------------------------
The problem is the burden that puts on the Yetus community. As an ASF community
their pre-release work is only supposed to be used by their community (which
gets defined by their dev@ list). Their PMC is charged with taking proactive
steps to avoid folks from outside that list using pre-release work. Right now
I'm relying on a rather liberal reading of that rule to justify myself and
other HBase folks who work on our precommit builds having a "check if the fix
for X works."
This is a big rabbit hole of ASF internals stuff I'd rather not waste energy
on. The number of cases where this impacts us should be minimal in the long
term. YETUS-280 is a temporary growing pain exacerbated by the Yetus project
still getting its feet on release cadence. It has a known work around that
literally any committer on the project can exercise.
> 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)
