[
https://issues.apache.org/jira/browse/SOLR-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506565#comment-14506565
]
Mike Drob commented on SOLR-7408:
---------------------------------
bq. Also, as the test that you've added is only useful when we manually add
breakpoints and debug, I guess it's a good idea to disable the test with that
comment and not increase the time taken to really run the tests on Jenkins.
What do you think?
It might be possible to reproduce the context switching/breakpoint behaviour by
inserting several countdown latches into the test. This might end up being more
trouble than it's worth, but attempting to reliably trigger race conditions can
be nearly impossible otherwise.
> Let SolrCore be the only thing which registers/unregisters a config directory
> listener
> --------------------------------------------------------------------------------------
>
> Key: SOLR-7408
> URL: https://issues.apache.org/jira/browse/SOLR-7408
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: SOLR-7408.patch, SOLR-7408.patch, SOLR-7408.patch,
> SOLR-7408.patch, SOLR-7408.patch, SOLR-7408.patch, SOLR-7408.patch
>
>
> As reported here: http://markmail.org/message/ynkm2axkdprppgef, there is a
> race condition which results in an exception when creating multiple
> collections over the same config set. I was able to reproduce it in a test,
> although I am only able to reproduce if I put break points and manually
> simulate the problematic context switches.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
