[
https://issues.apache.org/jira/browse/SOLR-11035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16096922#comment-16096922
]
Hoss Man commented on SOLR-11035:
---------------------------------
Amrit: because of the nature of the bug (concurrent threads w/o synchronization
or adequate locking) it's virtually impossible to write a test that is
garunteed to fail on any system. The test case i've attached just boils the
problematic scenerios down into their simplest essence.
If they pass reliably for you, i would suggest trying with diff seeds, and or
increasing the CPU load on your machine to force more thread switching in the
JVM (with something like {{stress}})
either way: As i described in my earlier comment (and as shalin described in
the linked issue) at least one of the problems is fairly self evident when
reading the code.
> (at least) 2 distinct failures possible when clients attempt searches during
> SolrCore reload
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-11035
> URL: https://issues.apache.org/jira/browse/SOLR-11035
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Attachments: log.txt, log.txt, SOLR-11035.patch
>
>
> If a SolrCore is reloaded, there are (at least) 2 distinct types of failures
> that clients may observe when executing updates + queries while the reload is
> in progress...
> * documents may appear missing during queries
> * queries may fail with "SolrException: openNewSearcher called on closed core"
> Details to follow in comment...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
