[
https://issues.apache.org/jira/browse/SOLR-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501174#comment-14501174
]
Shalin Shekhar Mangar commented on SOLR-7408:
---------------------------------------------
bq. I would personally prefer that we stop removing all listeners, and let a
core take care of itself, but I don't know how safe is Solr code in that
regard. I.e. are all places that create a SolrCore clean up after it in the
event of a failure? Clearly CoreAdminHandler.handleCreateAction doesn't, which
got me thinking what other places don't do that as well.
Should we start ref counting the ZK watches?
> 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
>
>
> 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]
