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

Anshum Gupta commented on SOLR-7038:
------------------------------------

CREATE call without any configset in SolrCloud:
http://localhost:8983/solr/admin/collections?action=CREATE&name=thisshouldfail&numShards=1&collection.configName=thisisaninvalidconfigset

Here's the exception that get's logged over and over again:
{code}
INFO  - 2015-01-26 21:54:16.536; 
org.apache.solr.cloud.overseer.ClusterStateMutator; building a new cName: c1
INFO  - 2015-01-26 21:54:16.536; org.apache.solr.cloud.overseer.ZkStateWriter; 
going to create_collection /collections/c1/state.json
ERROR - 2015-01-26 21:54:16.537; 
org.apache.solr.cloud.Overseer$ClusterStateUpdater; Exception in Overseer main 
queue loop
org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode 
for /collections/c1/state.json
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
        at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783)
        at 
org.apache.solr.common.cloud.SolrZkClient$9.execute(SolrZkClient.java:379)
        at 
org.apache.solr.common.cloud.SolrZkClient$9.execute(SolrZkClient.java:376)
        at 
org.apache.solr.common.cloud.ZkCmdExecutor.retryOperation(ZkCmdExecutor.java:61)
        at 
org.apache.solr.common.cloud.SolrZkClient.create(SolrZkClient.java:376)
        at 
org.apache.solr.cloud.overseer.ZkStateWriter.writePendingUpdates(ZkStateWriter.java:163)
        at 
org.apache.solr.cloud.overseer.ZkStateWriter.enqueueUpdate(ZkStateWriter.java:91)
        at 
org.apache.solr.cloud.Overseer$ClusterStateUpdater.processQueueItem(Overseer.java:337)
        at 
org.apache.solr.cloud.Overseer$ClusterStateUpdater.run(Overseer.java:247)
        at java.lang.Thread.run(Thread.java:745)
{code}

and the trace from the response:
{code}
trace": "org.apache.solr.common.SolrException\n\tat 
org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:737)\n\tat
 
org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:693)\n\tat
 
org.apache.solr.handler.admin.CollectionsHandler.handleCreateAction(CollectionsHandler.java:870)\n\tat
 
org.apache.solr.handler.admin.CollectionsHandler.handleRequestBody(CollectionsHandler.java:188)\n\tat
 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:144)\n\tat
 
org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:736)\n\tat
 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:261)\n\tat
 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:204)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)\n\tat
 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)\n\tat
 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577)\n\tat
 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125)\n\tat
 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)\n\tat 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059)\n\tat
 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)\n\tat
 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215)\n\tat
 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110)\n\tat
 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)\n\tat
 org.eclipse.jetty.server.Server.handle(Server.java:497)\n\tat 
org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:313)\n\tat 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248)\n\tat
 
org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540)\n\tat
 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:626)\n\tat
 
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:546)\n\tat
 java.lang.Thread.run(Thread.java:745)\n",
"code": 500
{code}

> If no configset exists, CREATE leads to a 500 error with never-ending logging 
> and 100% CPU usage
> ------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7038
>                 URL: https://issues.apache.org/jira/browse/SOLR-7038
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.0
>            Reporter: Anshum Gupta
>            Assignee: Anshum Gupta
>            Priority: Blocker
>             Fix For: 5.0, Trunk
>
>
> Here's what I did:
> {code}
> > bin/solr start -e cloud -noprompt
> > curl 
> > http://localhost:8983/solr/admin/collections?action=CREATE&name=thisshouldfail&numShards=1&configset=thisisaninvalidconfigset&wt=json
> {code}
> The above led to a new collection named thisshouldfail, with the config-set 
> as gettingstarted. This call should have failed as there was no configset by 
> that name. Instead, it picked up the only config set it found and used it.
> There's more to this. I'm not sure how related this is but looks like it to 
> me.
> {code}
> > bin/solr start -c
> > curl 
> > http://localhost:8983/solr/admin/collections?action=CREATE&name=thisshouldfail&numShards=1&configset=thisisaninvalidconfigset&wt=json
> {code}
> This led to a 900M (and growing) log file in addition to 100% CPU until I 
> killed Solr.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to