[
https://issues.apache.org/jira/browse/SOLR-13553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877263#comment-16877263
]
Noble Paul commented on SOLR-13553:
-----------------------------------
bq.Agree that clusterprops was not intended as a place to dump any and config
on the cluster level, even if it has a REST API.
Ideally, we should have a single file for storing every cluster-wide config.
The reason why {{clusterprops.json}} was added was only because {{solr.xml}}
was a read-only config. The ideal name was {{cluster-config.json}} which should
have had all the cluster-wide configuration. Now that the genie is out of the
bottle , I would just live with it instead of adding another file that we need
to manage.
bq. Can you mention a few examples of new handlers that will use this mechanism?
here are a few examples
* A handler to collect and get custom metrics
* A handler that can compute custom suggestions for autoscaling
> Node level custom RequestHandlers
> ---------------------------------
>
> Key: SOLR-13553
> URL: https://issues.apache.org/jira/browse/SOLR-13553
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
>
> These components
> * Available on every node
> * deployed at the {{CoreContainer}} level
> * Available at {{/solr/admin/<plugin-name> or {{/api/node/<plugin-name>}}
> (v2 style)
> * Should implement the {{SolrRequestHandler}} interface
> The configuration is persisted in {{clusterprops.json}}
> {code}
> curl -X POST -H 'Content-type:application/json' --data-binary '{
> "add-requesthandler": {
> "name": "/foo",
> "class" : "fully.qualified.ClassName"
>
> }
> }' http://localhost:8983/api/cluster
> {code}
> delete it using
> {code}
> curl -X POST -H 'Content-type:application/json' --data-binary '{
> "delete-requesthandler": "/foo"
> }' http://localhost:8983/api/cluster
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
