[ 
https://issues.apache.org/jira/browse/SOLR-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man reassigned SOLR-4373:
------------------------------

    Assignee: Mark Miller  (was: Hoss Man)

Mark: i really don't have anything to offer on this issue beyond the comments i 
already posted ... based on my testing it really _seems_ like this is caused by 
SOLR-4063, but that may be totally off base since aledandre couldn't make the 
problem go away using hte workarround i thought i found (ie: forcing single 
threaded core init)

since i couldn't reproduce a similar collision between multicores with a simple 
stopwords file loaded from the classpath, it also seems likeley that this 
relates to SPI loading: but since i don't really understand at all how 
NamedSPILoader works in a multiclassloader application (and since my 
experiements in forcing synchronization on it didn't solve the problem for me) 
i'm at a dead in there as well


                
> In multicore, lib directives in solrconfig.xml cause conflict and clobber 
> directives from earlier cores
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4373
>                 URL: https://issues.apache.org/jira/browse/SOLR-4373
>             Project: Solr
>          Issue Type: Bug
>          Components: multicore
>    Affects Versions: 4.1
>            Reporter: Alexandre Rafalovitch
>            Assignee: Mark Miller
>            Priority: Blocker
>              Labels: lib, multicore
>             Fix For: 4.2, 5.0, 4.1.1
>
>         Attachments: multicore-bug.zip
>
>
> Having lib directives in solrconfig.xml seem to wipe out/override the 
> definitions in previous cores.
> The exception (for the earlier core) is:
>       at 
> org.apache.solr.util.plugin.AbstractPluginLoader.load(AbstractPluginLoader.java:177)
>       at org.apache.solr.schema.IndexSchema.readSchema(IndexSchema.java:369)
>       at org.apache.solr.schema.IndexSchema.<init>(IndexSchema.java:113)
>       at 
> org.apache.solr.core.CoreContainer.createFromLocal(CoreContainer.java:1000)
>       at org.apache.solr.core.CoreContainer.create(CoreContainer.java:1033)
>       at org.apache.solr.core.CoreContainer$3.call(CoreContainer.java:629)
>       at org.apache.solr.core.CoreContainer$3.call(CoreContainer.java:624)
>       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>       at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>       at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>       at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>       at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.solr.common.SolrException: Plugin init failure for 
> [schema.xml] analyzer/filter: Error loading class 
> 'solr.ICUFoldingFilterFactory'
>       at 
> org.apache.solr.util.plugin.AbstractPluginLoader.load(AbstractPluginLoader.java:177)
>       at 
> org.apache.solr.schema.FieldTypePluginLoader.readAnalyzer(FieldTypePluginLoader.java:377)
>       at 
> org.apache.solr.schema.FieldTypePluginLoader.create(FieldTypePluginLoader.java:95)
>       at 
> org.apache.solr.schema.FieldTypePluginLoader.create(FieldTypePluginLoader.java:43)
>       at 
> org.apache.solr.util.plugin.AbstractPluginLoader.load(AbstractPluginLoader.java:151)
> The full replication case is attached.
> If the SECOND core is turned off in solr.xml, the FIRST core loads just fine.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to