lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaliy Zhovtyuk (JIRA)" <>
Subject [jira] [Commented] (SOLR-6678) Collection/core reload is causing a memory leak
Date Wed, 25 Feb 2015 19:55:05 GMT


Vitaliy Zhovtyuk commented on SOLR-6678:

i did 100K reload on techproducts and other cores and i cannot reproduce issue in heap dump.
Heap goes down after force GC.
Can you pls provide exact JRE version, options and solr config?

> Collection/core reload is causing a memory leak
> -----------------------------------------------
>                 Key: SOLR-6678
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.10
>            Reporter: Alexey Serba
>         Attachments: ReloadMemoryLeak.png
> I have a use case where I need to periodically [reload|]
a SolrCloud collection. Recently I did ~1k reload operations and noticed that the cluster
was running slower and slower, so I connected to it with jconsole and noticed that heap was
growing with every reload operation, forcing GC wasn't helping.
> So I took a heap dump and noticed that I have too many SolrCore-s hanging around. 
> It's hard for me to grok the root cause of this, but maybe someone more knowledgable
in Solr internals can figure it out by looking into this GC root path (see attached image)?
If I interpret this correctly, it looks like one SolrCore is referencing another SolrCore
through SolrSuggester. Maybe close hook for SolrSuggester component doesn't release everything
that it should be releasing (like SolrSuggester.dictionary)?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message