[
https://issues.apache.org/jira/browse/SOLR-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707531#comment-15707531
]
Erick Erickson commented on SOLR-7282:
--------------------------------------
The idea of sharing collections that are named differently but happen to be
exactly the same strikes me as added complexity for very little gain. And
tracking down errors in that world would be...interesting.
+1 to reusing the same objects if possible for configsets that have the same
znode (assuming it handles the mutable issue)
-1 to using a configset other than the one specified by the user when the
collection was created because we think it's the same based on the hash.
> 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
