lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4373) In multicore, lib directives in solrconfig.xml cause conflict and clobber directives from earlier cores
Date Tue, 26 Feb 2013 13:58:13 GMT

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

Alexandre Rafalovitch commented on SOLR-4373:
---------------------------------------------

I am trying to build the distribution to confirm, but - since it is my first time - not sure
what sequence of ant commands to run to get fully functioning example directory with all the
dist and contrib libraries in place. **run-example** does not seem to generate the dist/contrib
libraries and I am not using subversion for **distrib** command.

Wiki seems to be silent on that as well. Is there a new developer guide somewhere?
                
> 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


Mime
View raw message