[
https://issues.apache.org/jira/browse/SOLR-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906482#comment-13906482
]
Shawn Heisey commented on SOLR-5747:
------------------------------------
This would be a nice feature, but making it happen by default seems like a bad
idea to me. It would result in a considerable change to Solr's default
behavior. If we make it configurable and don't turn it on by default, I think
it would be nice to have.
Right now you can make a change to your config in zookeeper, and it won't take
effect until you CHOOSE to make it take effect, by reloading manually. If you
have several thousand collections all using the same config, you definitely
don't want thousands of cores to reload, even if it were to happen one-by-one
instead of all at once.
> 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]
