[
https://issues.apache.org/jira/browse/SOLR-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709440#comment-15709440
]
Scott Blum commented on SOLR-7282:
----------------------------------
Erick, apologies, I'm sick so I'm not explaining this well.
I'm not talking about doing anything contrary to what the user asked for. I am
only talking about a memory-saving implementation detail. If the internal
object representing a configset is in fact immutable and sharable, then there
is no user-facing difference as to whether two configsets with identical
content are internally represented by the same immutable sharable object or two
different but indistinguishable identical objects.
To answer your other questions we're not on an old solr, we're in solrcloud.
core.properties doesn't apply the config is in ZK. The problem is we have one
configset per collection. 4000 collections, 4000 configsets, all content
identical. Does MODIFYCOLLECTION actually allow you to change the configset a
particular collection points to? I swear last time I looked at that doc,
collection.configName wasn't in the list of things you could mutate.
> 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
