[
https://issues.apache.org/jira/browse/SOLR-11882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335996#comment-16335996
]
Erick Erickson commented on SOLR-11882:
---------------------------------------
What I see at this point is that the number of cores in memory is actually
capped by the total number of cores that have been defined. Say I have 30
transient cores and my transient core cache limit is 4. Eventually I see
exactly 30 cores in memory.
However, I have to stop my indexing program that's cycling through all the
cores and trigger a GC for the SolrCores to drop back to 30. So if I randomly
sample the number of Solr cores it'll be between 40-50 (or more, depending on
how much free memory I have allocated) as the stress program is running, but
when I stop indexing and trigger a GC, it drops back to exactly 30.
Does that square with what you see? This is still a problem of course, it
should drop back to 4.
> SolrMetric registries cause huge memory consumption with lots of transient
> cores
> --------------------------------------------------------------------------------
>
> Key: SOLR-11882
> URL: https://issues.apache.org/jira/browse/SOLR-11882
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server
> Affects Versions: 7.1
> Reporter: Eros Taborelli
> Assignee: Erick Erickson
> Priority: Major
> Attachments: SOLR-11882.patch, create-cores.zip,
> solr-dump-full_Leak_Suspects.zip, solr.config.zip
>
>
> *Description:*
> Our setup involves using a lot of small cores (possibly hundred thousand),
> but working only on a few of them at any given time.
> We already followed all recommendations in this guide:
> [https://wiki.apache.org/solr/LotsOfCores]
> We noticed that after creating/loading around 1000-2000 empty cores, with no
> documents inside, the heap consumption went through the roof despite having
> set transientCacheSize to only 64 (heap size set to 12G).
> All cores are correctly set to loadOnStartup=false and transient=true, and we
> have verified via logs that the cores in excess are actually being closed.
> However, a reference remains in the
> org.apache.solr.metrics.SolrMetricManager#registries that is never removed
> until a core if fully unloaded.
> Restarting the JVM loads all cores in the admin UI, but doesn't populate the
> ConcurrentHashMap until a core is actually fully loaded.
> I reproduced the issue on a smaller scale (transientCacheSize = 5, heap size
> = 512m) and made a report (attached) using eclipse MAT.
> *Desired outcome:*
> When a transient core is closed, the references in the SolrMetricManager
> should be removed, in the same fashion the reporters for the core are also
> closed and removed.
> In alternative, a unloadOnClose=true|false flag could be implemented to fully
> unload a transient core when closed due to the cache size.
> *Note:*
> The documentation mentions everywhere that the unused cores will be unloaded,
> but it's misleading as the cores are never fully unloaded.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
