[
https://issues.apache.org/jira/browse/SOLR-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024672#comment-17024672
]
Chris M. Hostetter commented on SOLR-14040:
-------------------------------------------
FWIW: TestBulkSchemaConcurrent was failing a lot on master as well after your
original commit, but the master failures seemed to have dropped off after your
Jan22 commits while the 8x failures continued.
I have not dug into the logs from the failures to compare 8x / master (or 8x
bbefore/after your "restore legacy Collection auto-creation" commits) to see if
the *nature* of the failures is diff – but you might want to before they get
purged (my report system only keeps the past 7 days worth of logs due to disk
constraints)
> 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
> Components: Schema and Analysis
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Fix For: 8.5
>
> Time Spent: 0.5h
> 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
