[ 
https://issues.apache.org/jira/browse/SOLR-14182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242285#comment-17242285
 ] 

Andrzej Bialecki commented on SOLR-14182:
-----------------------------------------

I'd like to start working on this. As I see it this issue needs to address the 
following:
 * mark {{solr.xml:/solr/metrics}} as deprecated and remove in 9.1.
 * general metrics configuration (such as enable/disable, metric suppliers 
options) should move to {{/clusterprops.json:/metrics}}
 * metric reporters configuration should be moved to container-level plugins, 
ie. {{/clusterprops.json:/plugin}} and the corresponding API. This will make 
the reporters easier to configure and change dynamically without restarting 
Solr nodes.
 * precedence: {{MetricsConfig}} will be initialized from {{solr.xml}} as 
before. Then, if any clusterprops configuration is present then it will REPLACE 
the one fromĀ {{solr.xml}} - I don't want to attempt any fusion of these two, 
and I think it's easier to migrate if you don't merge these configs. This 
approach means that defining anything using the new locations will 
automatically turn off the old {{solr.xml}} config.

> Move metric reporters config from solr.xml to ZK cluster properties
> -------------------------------------------------------------------
>
>                 Key: SOLR-14182
>                 URL: https://issues.apache.org/jira/browse/SOLR-14182
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 8.4
>            Reporter: Andrzej Bialecki
>            Assignee: Andrzej Bialecki
>            Priority: Major
>
> Metric reporters are currently configured statically in solr.xml, which makes 
> it difficult to change dynamically or in a containerized environment.
> We should move this section to ZK /cluster.properties and add a back-compat 
> migration shim.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to