You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jessica Cheng Mallet (JIRA)" <ji...@apache.org> on 2016/05/16 17:04:12 UTC

[jira] [Created] (SOLR-9117) Leaking the first SolrCore after reload

Jessica Cheng Mallet created SOLR-9117:
------------------------------------------

             Summary: Leaking the first SolrCore after reload
                 Key: SOLR-9117
                 URL: https://issues.apache.org/jira/browse/SOLR-9117
             Project: Solr
          Issue Type: Bug
            Reporter: Jessica Cheng Mallet
         Attachments: SOLR-9117.patch

When a SolrCore for a particular index is created for the first time, it's added to the SolrCores#createdCores map. However, this map doesn't get updated when this core is reloaded, leading to the first SolrCore being leaked.

Taking a look at how createdCores is used, it seems like it doesn't serve any purpose (its only read is in SolrCores#getAllCoreNames, which includes entries from SolrCores.cores anyway), so I'm proposing a patch to remove the createdCores map completely. However, if someone else knows that createdCores exist for a reason, I'll be happy to change the fix to updating the createdCores map when reload is called.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org