[ 
https://issues.apache.org/jira/browse/SOLR-14040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050531#comment-17050531
 ] 

Noble Paul commented on SOLR-14040:
-----------------------------------

There are a few of fundamental problems with the way this is implemented

# The first time the {{IndexSchema}} is created, it uses the 
{{SolrResourceLoader}} of the first core lets's call it {{SRL1}}. When another 
core comes up, it gets another {{SolrResourceLoader}} {{SRL2}} . The components 
loaded for core2 uses {{SRL2}} and the {{IndexSchema}} it's gonna use uses 
{{SRL1}} (because it is shared). This can cause {{ClassCastException}} if the 
per core component is sharing an object with schema
# As the core2 is still holding on to the shared schema, it is in turn holding 
a reference to SRL1 . So, even if core1 is unloaded , it is not fully garbage 
collected & the classes & objects can linger on 

What can we do?

# Revert this and have a proper design & implement everything correctly in the 
next release
# Mark this as experimental & give a warning to users that this is faulty






> 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

Reply via email to