[ https://issues.apache.org/jira/browse/SOLR-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709514#comment-15709514 ]
Shawn Heisey commented on SOLR-7282: ------------------------------------ The way that I was always aware of for changing this in cloud mode is zkcli, using the linkconfig command. Followed of course by a collection reload. I wasn't even really aware of MODIFYCOLLECTION until just now ... the docs do say that you can update collection.configName. SOLR-5132 (which implemented MODIFYCOLLECTION) says that the intent was to automatcially a reload in the event the configname was modified. I don't know if the automatic reload was implemented. https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-modifycoll > Cache config or index schema objects by configset and share them across cores > ----------------------------------------------------------------------------- > > Key: SOLR-7282 > URL: https://issues.apache.org/jira/browse/SOLR-7282 > Project: Solr > Issue Type: Sub-task > Components: SolrCloud > Reporter: Shalin Shekhar Mangar > Assignee: Noble Paul > Fix For: 5.2, 6.0 > > Attachments: SOLR-7282.patch > > > Sharing schema and config objects has been known to improve startup > performance when a large number of cores are on the same box (See > http://wiki.apache.org/solr/LotsOfCores).Damien also saw improvements to > cluster startup speed upon caching the index schema in SOLR-7191. > Now that SolrCloud configuration is based on config sets in ZK, we should > explore how we can minimize config/schema parsing for each core in a way that > is compatible with the recent/planned changes in the config and schema APIs. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org