You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2017/05/22 18:21:04 UTC
[jira] [Commented] (SOLR-9803) Memory leak when creating/deleting
collections in VersionBucket
[ https://issues.apache.org/jira/browse/SOLR-9803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019952#comment-16019952 ]
Erick Erickson commented on SOLR-9803:
--------------------------------------
FWIW, this is still a problem on master.
> Memory leak when creating/deleting collections in VersionBucket
> ---------------------------------------------------------------
>
> Key: SOLR-9803
> URL: https://issues.apache.org/jira/browse/SOLR-9803
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.4
> Reporter: Erick Erickson
> Attachments: Main.java
>
>
> I was doing some stress testing for creating/deleting collections to see if SOLR-7936 was still a problem when I noticed memory creep. I'll attach the program I was using, but basically it creates/deletes a collection over and over.
> A little while after it starts, org.apache.solr.update.VersionBucket instances are
> bytes instances
> 18M 786K
> Then after 300+ iterations the numbers are:
> bytes instances
> 506M 21M
> jconsole shows an increasing heap usage as well.
> Whether the Solr node is an overseer or not is irrelevant.
> [~tpot] you might have some insight here?
> I also have no idea whether this more widespread than creating/deleting collections, it just happens that that was the test I was running when I saw this.
> I saw this on trunk, I assume 6x shows it too.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org