lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre GOSSÉ <>
Subject RE: Cloud and cores
Date Wed, 01 Aug 2012 15:43:19 GMT
It may have something to do with SOLR-3425, but I'm not that sure it fits.

I made some more tests.

Case 1 : with SolrCloud
I can create a new core on one of the server by the admin GUI or by CREATE directive in URL.
The data folder is created (but no conf folder, I believe zk conf is used). However ./solr/solr.xml
is not updated with the new core parameter.
If I restart the server, the core is lost (but data folder is kept)

Case 2 : on a single solr server
Creation of new core fails by the gui with error :
GRAVE: org.apache.solr.common.SolrException: Error executing default implementation of CREATE
        at org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(
        at org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(
        at org.apache.solr.handler.RequestHandlerBase.handleRequest(
        at org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(
        at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
        at org.eclipse.jetty.servlet.ServletHandler.doScope(
        at org.eclipse.jetty.server.session.SessionHandler.doScope(
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(
        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
        at org.eclipse.jetty.server.Server.handle(
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(
        at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(
        at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(
        at org.eclipse.jetty.http.HttpParser.parseNext(
        at org.eclipse.jetty.http.HttpParser.parseAvailable(

        at org.eclipse.jetty.server.BlockingHttpConnection.handle(
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
        at org.eclipse.jetty.util.thread.QueuedThreadPool$
        at Source)
Caused by: java.lang.RuntimeException: Can't find resource 'solrconfig.xml' in classpath or
'solr\core2\conf/', cwd=F:\solr-4.0\Test
        at org.apache.solr.core.SolrResourceLoader.openResource(
        at org.apache.solr.core.SolrResourceLoader.openConfig(
        at org.apache.solr.core.Config.<init>(
        at org.apache.solr.core.Config.<init>(
        at org.apache.solr.core.SolrConfig.<init>(
        at org.apache.solr.core.CoreContainer.create(
        at org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(
        ... 29 more

Using an URL CREATE and giving relative pathes for solrconfig.xml and shema.xml fails later
on stopwords.txt

Again solr/solr.xml is not updated, but the runtime exception could explain that in this case.

-----Message d'origine-----
De : Pierre GOSSÉ [] 
Envoyé : mercredi 1 août 2012 16:22
À :
Objet : Cloud and cores

Hi all,

I'm playing around with SolrCloud and followed indications I found at

-          Started Instance 1 with embedded zk

-          Started Instances 2 3 and 4 using Instance 1 as zk server.

Everything works fine.

Then, using CoreAdmin, I add a second core in collection1 for Instance 1 and 3 ... everything
is ok in the admin GUI, meaning that the graph show 2 shards of 3 server addresses each, those
having 2 cores showing to time on the graph.

collection1          shard1                  wks-pge:7574
shard2                  wks-pge:8983

On instances 1 and 3 I have 2 cores both at the bottom of the left column, and in the CoreAdmin

I restart everything, and find the server in what seems to be an inconsistent state : i.e.
graph still showing 2 shards of 3 server addresses, but CoreAdmin not showing my additional
cores any more.

Is there a problem in SolrCloud or CoreAdmin, or did I just do something stupid here ? :)


View raw message