You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/03/12 17:49:00 UTC
[jira] [Updated] (SOLR-17700) CoreContainer does not obtain a lock when unloading cores
[ https://issues.apache.org/jira/browse/SOLR-17700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated SOLR-17700:
----------------------------------
Labels: pull-request-available (was: )
> CoreContainer does not obtain a lock when unloading cores
> ---------------------------------------------------------
>
> Key: SOLR-17700
> URL: https://issues.apache.org/jira/browse/SOLR-17700
> Project: Solr
> Issue Type: Bug
> Reporter: Houston Putman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CoreContainer uses {{solrCores.waitAddPendingCoreOps(name)}} when doing an operation on a core. And the documentation for {{SolrCores.waitAddPendingCoreOps(name)}} mentions that:
> bq. // Wait here until any pending operations (load, unload or reload) are completed on this core.
> However, CoreContainer does not use this locking when unloading a core. This is the reason why we are seeing race condition issues when deleting and reloading a collection at the same time.
> Loading a core can possibly require unloading said core, when "deleteUnknownCoresOnStartup" is used, thus we need a way of unloading without a lock. But other than this edge case, locking the unload operation should only improve stability in Solr.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org