You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2016/06/17 21:39:05 UTC

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

     [ https://issues.apache.org/jira/browse/SOLR-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Rowe reopened SOLR-9117:
------------------------------

Reopening to backport to 5.6 and 5.5.2.

> 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
>            Assignee: Shalin Shekhar Mangar
>              Labels: core, leak
>             Fix For: 5.6, 6.0.1, 6.1, 5.5.2, master (7.0)
>
>         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