[
https://issues.apache.org/jira/browse/SOLR-8389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199993#comment-16199993
]
Amrit Sarkar commented on SOLR-8389:
------------------------------------
Hi Peter,
Absolutely, this serves and solves the purpose. I was about to go to down the
lines of autoscaling, glad you already worked that out. Couple of points I want
to lay out specific for CDCR:
1. The CDCR configurations will be uploaded at the time of collection creation.
Calling the api, collection-props, you are working on, implicitly can be called
if cdcr is involved.
2. The idea is to keep cdcr away from {{state.json}}, so that it doesn't get
rewritten by any node status change. I think the motivation of creating
collection properties is the same, if not wrong.
Looking forward to your patch and ultimately in the code, so that I can extend
the same to regulate cdcr configurations and actions. Thanks Peter.
> 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]
