lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tommaso Teofili (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3477) SOLR does not start up when no cores are defined
Date Wed, 30 May 2012 06:51:23 GMT

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

Tommaso Teofili commented on SOLR-3477:
---------------------------------------

I just tested this doesn't apply to Solr 4 thus I think this issue can be marked as resolved
with Fix Version 4.0.
Sebastian, can you also check if your scenario works with Solr 4?
                
> SOLR does not start up when no cores are defined
> ------------------------------------------------
>
>                 Key: SOLR-3477
>                 URL: https://issues.apache.org/jira/browse/SOLR-3477
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>    Affects Versions: 3.6
>         Environment: All environments
>            Reporter: Sebastian Schaffert
>            Priority: Critical
>
> Since version 3.6.0, Solr does not start up when no cores are defined in solr.xml. The
problematic code is in CoresContainer.java, lines 171-173.
> org.apache.solr.common.SolrException: No cores were created, please check the logs for
errors
> 	at org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.java:172)
~[solr-core-3.6.0.jar:3.6.0 1310449 - rmuir - 2012-04-06 11:34:38]
> 	at org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:96) ~[solr-core-3.6.0.jar:3.6.0
1310449 - rmuir - 2012-04-06 11:34:38]
> ...
> In our case, this is however a valid situation, because we create the cores programatically
by calling the webservices to register new cores. The server is initially started with no
cores defined, and depending on the configuration of our application, cores are then created
dynamically.
> For the time being, we have to stick with version 3.5, which did not have this problem
(or feature).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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