[
https://issues.apache.org/jira/browse/SOLR-14201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024584#comment-17024584
]
Christine Poerschke commented on SOLR-14201:
--------------------------------------------
Thanks [~vinhlh] for sharing these steps to reproduce the issue, and details of
the unreleased classes.
I notice that 'optimise' and 'alias' use is part of the steps; if one or both
of them was omitted and the issue then did or did not continue to happen, that
might provide further insights, if not already tried?
Specifically w.r.t. the 'optimise' step, it might be interesting to explore if
the optimise has finished by the time the collection deletion is requested.
[~GoodmanR]'s SOLR-13609 ticket is also about visibility into optimise progress.
> some SolrCore are not released after being removed
> --------------------------------------------------
>
> Key: SOLR-14201
> URL: https://issues.apache.org/jira/browse/SOLR-14201
> Project: Solr
> Issue Type: Bug
> Reporter: Christine Poerschke
> Priority: Major
> Attachments: image-2020-01-22-10-39-15-301.png,
> image-2020-01-22-10-42-17-511.png, image-2020-01-22-12-28-46-241.png,
> image-2020-01-22-14-45-52-730.png
>
>
> [~vinhlh] reported in SOLR-10506 (affecting 6.5 with fixes in 6.6.6 and 7.0):
> bq. In 7.7.2, some SolrCore still are not released after being removed.
> https://issues.apache.org/jira/secure/attachment/12991357/image-2020-01-20-14-51-26-411.png
> Starting this ticket for a separate investigation and fix. A next
> investigative step could be to try and reproduce the issue on the latest 8.x
> release.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
