[
https://issues.apache.org/jira/browse/SOLR-9867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781464#comment-15781464
]
Varun Thacker commented on SOLR-9867:
-------------------------------------
Yeah this problem seems to be with other examples as well:
Steps to reproduce:
{code}
./bin/solr start -e techproducts
./bin/solr stop
./bin/solr start -e techproducts
{code}
The third step causes the problem:
When we start since techproducts already exists , the start script fails to see
that and tries to create the core again leaving Solr in a bad state.
This doesn't happen in Solr 6.2.1 but happens in Solr 6.3
Here is the message I get when I run the third step in Solr 6.2.1
{code}
solr-6.2.1$ ./bin/solr start -e techproducts
Solr home directory ~/solr-6.2.1/example/techproducts/solr already exists.
Starting up Solr on port 8983 using command:
bin/solr start -p 8983 -s "example/techproducts/solr"
Waiting up to 30 seconds to see Solr running on port 8983 [|]
Started Solr server on port 8983 (pid=16088). Happy searching!
WARNING: Core 'techproducts' already exists!
Checked core existence using Core API command:
http://localhost:8983/solr/admin/cores?action=STATUS&core=techproducts
Solr techproducts example launched successfully. Direct your Web browser to
http://localhost:8983/solr to visit the Solr Admin UI
{code}
> The schemaless example can not be started after being stopped.
> --------------------------------------------------------------
>
> Key: SOLR-9867
> URL: https://issues.apache.org/jira/browse/SOLR-9867
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
>
> I'm having trouble when I start up the schemaless example after shutting down.
> I first tracked this down to the fact that the run example tool is getting an
> error when it tries to create the SolrCore (again, it already exists) and so
> it deletes the cores instance dir which leads to tlog and index lock errors
> in Solr.
> The reason it seems to be trying to create the core when it already exists is
> that the run example tool uses a core status call to check existence and
> because the core is loading, we don't consider it as existing. I added a
> check to look for core.properties.
> That seemed to let me start up, but my first requests failed because the core
> was still loading. It appears CoreContainer#getCore is supposed to be
> blocking so you don't have this problem, but there must be an issue, because
> it is not blocking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
