[
https://issues.apache.org/jira/browse/SOLR-9867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994993#comment-15994993
]
Mikhail Khludnev commented on SOLR-9867:
----------------------------------------
[~mdrob],
bq. perhaps, instead of latch we can assign cores strictly at the end of init.
What do you think?
Indeed! Thanks for the hint!
bq. Depends on if we want early requests to fail or to wait, no?
I suppose it's fine since we already have this check.
bq. couldn't this take a while? How did you decide 10 seconds?
I hardly remember how exactly I get to it. Now I set it to 30 sec (almost no
one experience it, since most of the users wait till Solr load cores before
stop it), internally it makes 0.5 sec polls, so it doesn't really matter. But
I'm happy to put any number there which makes tests pass.
> 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]
