You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Rene Nederhand (JIRA)" <ji...@apache.org> on 2013/03/01 21:35:12 UTC

[jira] [Commented] (SOLR-4373) In multicore, lib directives in solrconfig.xml cause conflict and clobber directives from earlier cores

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

Rene Nederhand commented on SOLR-4373:
--------------------------------------

I'm still experiencing the same problems (rev 1450937): Libraries cannot be found. 

Moreover, the workaround by adding {{coreLoadThreads="1"}} to solr.xml does not work in SolrCloud. I get: "SolrCloud requires a value of at least 2 in solr.xml for coreLoadThreads".

One additional observation: The first time I create a core it fails, however the second time it succeeds. Does anyone knows why it happens? FYI: I am attaching the test script I am using to upload, link the config and create the cores.
                
> 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
>            Priority: Blocker
>              Labels: lib, multicore
>             Fix For: 4.2, 5.0, 4.1.1
>
>         Attachments: multicore-bug.zip
>
>
> Having lib directives in the solrconfig.xml files of multiple cores can cause problems when using multi-threaded core initialization -- which is the default starting with Solr 4.1.
> The problem manifests itself as init errors in the logs related to not being able to find classes located in plugin jars, even though earlier log messages indicated that those jars had been added to the classpath.
> One work around is to set {{coreLoadThreads="1"}} in your solr.xml file -- forcing single threaded core initialization.  For example...
> {code}
> <?xml version="1.0" encoding="utf-8" ?>
> <solr coreLoadThreads="1">
>   <cores adminPath="/admin/cores">
>     <core name="core1" instanceDir="core1" />
>     <core name="core2" instanceDir="core2" />
>   </cores>
> </solr>
> {code}
> (Similar problems may occur if multiple cores are initialized concurrently using the /admin/cores handler)

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org