Anshum Gupta created SOLR-7038:
----------------------------------
Summary: If configset for a new collection doesn't exist, it picks
up the only config available
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.
{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]
