[
https://issues.apache.org/jira/browse/SOLR-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17019625#comment-17019625
]
David Smiley commented on SOLR-14040:
-------------------------------------
This optimization was huge to Salesforce's situation involving ~2000 live
SolrCores and large schemas referring to heavy objects. The benefit is both in
memory and core startup time -- the latter helps the utility of transient cores
being viable. We're ensuring this optimization works in SolrCloud as well as
it already does in standalone Solr. There was definitely an analysis proving
this out. We ought to re-do one in SolrCloud mode as I fear there are
new/additional speed bumps slowing core loading.
> solr.xml shareSchema does not work in SolrCloud
> -----------------------------------------------
>
> Key: SOLR-14040
> URL: https://issues.apache.org/jira/browse/SOLR-14040
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Schema and Analysis
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> solr.xml has a shareSchema boolean option that can be toggled from the
> default of false to true in order to share IndexSchema objects within the
> Solr node. This is silently ignored in SolrCloud mode. The pertinent code
> is {{org.apache.solr.core.ConfigSetService#createConfigSetService}} which
> creates a CloudConfigSetService that is not related to the SchemaCaching
> class. This may not be a big deal in SolrCloud which tends not to deal well
> with many cores per node but I'm working on changing that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
