[
https://issues.apache.org/jira/browse/SOLR-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16203842#comment-16203842
]
Peter Rusko commented on SOLR-8389:
-----------------------------------
The main concern was exactly the update frequency, that's why I separated this
from state.json, to clusterprops.json. It will have its own watcher and won't
be affected by clusterstate changes. The intention was to put user-defined
properties here, which can be changed without restarting solr.
Varun, I'm not sure what you mean by that. Currently unrelated collection
property changes still trigger all the listeners, but given that they are all
supposed to be rare (though nothing prevents anyone from writing properties
from the code I guess), I don't see this as a problem.
> Convert CDCR peer cluster and other configurations into collection properties
> modifiable via APIs
> -------------------------------------------------------------------------------------------------
>
> Key: SOLR-8389
> URL: https://issues.apache.org/jira/browse/SOLR-8389
> Project: Solr
> Issue Type: Improvement
> Components: CDCR, SolrCloud
> Reporter: Shalin Shekhar Mangar
>
> CDCR configuration is kept inside solrconfig.xml which makes it difficult to
> add or change peer cluster configuration.
> I propose to move all CDCR config to collection level properties in cluster
> state so that they can be modified using the existing modify collection API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
