[
https://issues.apache.org/jira/browse/SOLR-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906792#comment-13906792
]
Daniel Collins commented on SOLR-5747:
--------------------------------------
I'd agree with Shawn/Mark, for a large production system, having it
automatically pick up new configuration feels positively dangerous. Our
production systems need more fine-grained control over when replicas are
reloaded, so operationally, we upload new config, and then restart parts of the
cloud piece by piece. This also reduces our load on ZK (we have 1024 cores, so
it they all receive a watch at the same time, and start pulling config, its a
non-trivial load on ZK, and the poor old Overseer gets swamped!)
I can understand automatic deployment in a development system (definitely
easier I grant you), or maybe small-scale production (depends what
rollout/backout you have to handle) but seems more of a nice to have than
important. But I guess it depends on your use case.
> Update the config need manual restart the cluster server.
> ---------------------------------------------------------
>
> Key: SOLR-5747
> URL: https://issues.apache.org/jira/browse/SOLR-5747
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.5, 4.5.1, 4.6, 4.6.1
> Environment: linux, solr cloud
> Reporter: Raintung Li
> Labels: collection, config
> Attachments: patch-5747
>
>
> Many collections bundle one config. If I update the config, I need manual
> reload the collection one by one.
> Could monitor config for every collection. If update the config, the monitor
> will notify and automatic reload collection for every solr core.
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
