[
https://issues.apache.org/jira/browse/SOLR-7282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15709228#comment-15709228
]
Scott Blum edited comment on SOLR-7282 at 11/30/16 5:43 PM:
------------------------------------------------------------
I mean, content hashing is a pretty ubiquitous technique. Git is fundamentally
built on it.
The reason I personally care is that our cluster is so old I'm not even sure if
configsets were a thing when we started. So we have 4000 collections with 4000
identical configurations.
Is there even a way to change an existing collection to use a configset?
was (Author: dragonsinth):
I mean, content hashing is a pretty ubiquitous technique. Git is fundamentally
built on it.
The reason I personally care is that our cluster is so old I'm not even sure if
configsets were a thing when we started. So we have 4000 collections with 4000
identical configurations.
> 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: [email protected]
For additional commands, e-mail: [email protected]
