[
https://issues.apache.org/jira/browse/SOLR-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-6879:
--------------------------------
Attachment: SOLR-6879.patch
Patch with a test case.
I found a bug in how the Overseer deals with a CLUSTERPROP event. The switch
case does not break. I have fixed it in the same patch. Should I create another
Jira for it if we want to backport this to the 4.x branch?
> Have an option to disable autoAddReplicas temporarily for all collections
> -------------------------------------------------------------------------
>
> Key: SOLR-6879
> URL: https://issues.apache.org/jira/browse/SOLR-6879
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Attachments: SOLR-6879.patch
>
>
> When doing offline maintenance on my cluster I would like to disable
> autoAddReplicas since I don't want replicas being created on nodes during
> this time.
> It would be useful to have an option to enable/disable autoAddReplicas via an
> API.
> This API would disable autoAddReplicas:
> {code}
> admin/collections?action=CLUSTERPROP&name=autoAddReplicas&val=false
> {code}
> Now when I want to enable it again the API call would look like this:
> {code}
> admin/collections?action=CLUSTERPROP&name=autoAddReplicas
> {code}
> This uses the CLUSTERPROP semantics of unsetting a property when the {{val}}
> param is not provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
