[
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.patch] is on 6x. It enables {{testTechproductsExample}} and makes
{{beast}} happy about it. Therefore, there should be some work to fix tests,
which are currently failing on ci.
- the patch makes core status aware of loading cores and latches
SolrDispatchFilter.doFilter on init. Otherwise, status request might be handled
before core starts load in background. I always though that a servlet container
provides init/doFilter latching, so naive.
- perhaps, instead of latch we can assign {{cores}} strictly at the end of
{{init}}. What do you think?
- patch also blocks container closing, until core loading is stopped with
failure.
- and also it makes run example tool spin until core is loaded before search.
Concerns?
> 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.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
