[
https://issues.apache.org/jira/browse/SOLR-9867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-9867:
-----------------------------------
Attachment: SOLR-9867.patch
SOLR-9867-ignore-whitespace.patch
also attaching [^SOLR-9867-ignore-whitespace.patch] to make review easier since
original [^SOLR-9867.patch] has too many identations.
h3. Key stuff
* I've removed SDF.init() latch, and just assign volatile {{SDF.cores}} at the
end of {{init()}} since SDF.doFilter() already has a precondition check
{{SDF.cores!=null}}.
* this change introduces new {{/admin/cores?action=STATUS&}} response:
{code}
{ name:foo, isLoaded:false, isLoading:true }
{code}
* {{SolrCLI}} waits for a core to come up 1 min max with 1 sec poll interval.
h3. BTW
What about committing it tomorrow?
h3. Also
All {{TestSolrCLIRunExample}} tests runs just for 47 secs at my laptop. Should
it still be marked as {{@Slow}}
> The Solr examples can not always be started after being stopped due to race
> with loading core.
> ----------------------------------------------------------------------------------------------
>
> 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
> Priority: Critical
> Fix For: 6.6, master (7.0)
>
> Attachments: SDF init and doFilter in parallel.png,
> SOLR-9867-ignore-whitespace.patch, SOLR-9867.patch, SOLR-9867.patch,
> SOLR-9867.patch, SOLR-9867.patch, SOLR-9867.patch, SOLR-9867-test.patch
>
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
