[
https://issues.apache.org/jira/browse/HBASE-9774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-9774:
---------------------------------
Attachment: hbase-9774_v5.patch
Found the issue that was affecting the tests. It is due to the fact that we are
registering metrics inside the getMetrics() method. Although there is the
MetricsSystemImpl monitor for synchronization, this happens due to the lock
being re-entrant. Changed the code for GlobalMetricRegistriesSource to use an
executor instead to register the metrics.
Let's see what hadoopqa thinks.
> Provide a way for coprocessors to register and report custom metrics
> --------------------------------------------------------------------
>
> Key: HBASE-9774
> URL: https://issues.apache.org/jira/browse/HBASE-9774
> Project: HBase
> Issue Type: New Feature
> Components: Coprocessors, metrics
> Reporter: Gary Helmling
> Assignee: Enis Soztutar
> Attachments: hbase-9774_v1.patch, hbase-9774_v3.patch,
> hbase-9774_v4.patch, hbase-9774_v5.patch
>
>
> It would help provide better visibility into what coprocessors are doing if
> we provided a way for coprocessors to export their own metrics. The general
> idea is to:
> * extend access to the HBase "metrics bus" down into the coprocessor
> environments
> * coprocessors can then register and increment custom metrics
> * coprocessor metrics are then reported along with all others through normal
> mechanisms
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
