Varun Thacker created SOLR-10534:
------------------------------------
Summary: Core state doesn't get cleaned up if core initialization
fails
Key: SOLR-10534
URL: https://issues.apache.org/jira/browse/SOLR-10534
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Varun Thacker
Steps to reproduce:
Add this to the "add-unknown-fields-to-the-schema" in the data_driven config set
{code}
<processor class="solr.DocBasedVersionConstraintsProcessorFactory">
<str name="versionField">_version_</str>
</processor>
{code}
./bin/solr start
./bin/solr create -c test
This doesn't work currently because of SOLR-10533 so it throws an error when
creating a core.
At this point I have no local core created for 'test' but the UI displays
'SolrCore initalization failures'
Now let's fix the schema and remove the update processor
Running the create command again throws this error but I don't have this core.
{code
~/solr-6.5.0$ ./bin/solr create -c test
ERROR:
Core 'test' already exists!
Checked core existence using Core API command:
http://localhost:8983/solr/admin/cores?action=STATUS&core=test
{code}
When I restart and then try again it work correctly.
The same happens in SolrCloud as well but the experience is even worse.
Since no collection was never created but a local core exists the create
command blocks and then after a while returns with an error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
