[jira] [Commented] (SOLR-7056) Disable Collections API during rolling upgrade

["Jan Høydahl (Jira)" <ji...@apache.org>]

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

Jan Høydahl commented on SOLR-7056:
-----------------------------------

+1

Also cluster-level commands should be disabled, i.e. {{/api/cluster}}.

During a rolling upgrade, we'd likely also want to disable any form of autoscaling actions that may be triggered (stuff in {{org.apache.solr.cluster.events}}), so that people's custom plugins won't start reacting to NODES_DOWN events, moving replicas around... But that's likely a separate command.

> Disable Collections API during rolling upgrade
> ----------------------------------------------
>
>                 Key: SOLR-7056
>                 URL: https://issues.apache.org/jira/browse/SOLR-7056
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>         Environment: 
>            Reporter: Hrishikesh Gadre
>            Priority: Major
>
> As per Mark,
> "bq.  want to upgrade note a recommendation to not run collections api commands while doing the rolling upgrade
> The more I think about this, the more this makes sense in general, for any rolling upgrades. We should remove this java serialization, but I think creating or modifying a collection across versions is probably never a wonderful idea. We might want to add an easy way to enable / disable such API's even."



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org