lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] [Resolved] (SOLR-11221) SolrJmxReporter broken on core reload
Date Mon, 21 Aug 2017 10:44:02 GMT


Andrzej Bialecki  resolved SOLR-11221.
    Resolution: Fixed

> SolrJmxReporter broken on core reload
> -------------------------------------
>                 Key: SOLR-11221
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: metrics
>    Affects Versions: 6.6, 7.0, 6.7, master (8.0)
>            Reporter: Andrzej Bialecki 
>            Assignee: Andrzej Bialecki 
>            Priority: Critical
>             Fix For: 7.0, 6.6.1, master (8.0), 7.1
>         Attachments: SOLR-11221.patch
> {{SolrJmxReporter}} uses Dropwizard's {{JmxReporter}}, which in turn uses a {{MetricRegistry}}
listener to report newly added metrics as MBeans, and to unregister them from MBeanServer
when the reporter is closed, which happens when core is closed.
> The metrics API keeps around existing metrics in {{solr.core.*}} registries to help maintain
continuous metrics in presence of core reloads. However, this means that some of these metric
instances are not registered anew when a core is reloaded - and for these metrics the listener
won't fire, so the MBeans won't be registered.
> This limitation is a result of the use of {{MetricRegistryListener}} in {{JmxReporter}}
and can't be fixed without reimplementing this class. Another possible approach would be to
configure the {{JmxReporter}} to use a "mirroring" registry instead, which will be populated
with existing metrics from the original registry (thus generating "metric added" events) and
then kept in sync with the main registry via a listener.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message