You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/02/27 19:28:04 UTC
[jira] [Created] (OAK-2557) VersionGC uses way too much memory if
there is a large pile of garbage
Stefan Egli created OAK-2557:
--------------------------------
Summary: VersionGC uses way too much memory if there is a large pile of garbage
Key: OAK-2557
URL: https://issues.apache.org/jira/browse/OAK-2557
Project: Jackrabbit Oak
Issue Type: Bug
Components: core, mongomk
Affects Versions: 1.0.11
Reporter: Stefan Egli
It has been noticed that on a system where revision-gc (VersionGarbageCollector of mongomk) did not run for a few days (due to not interfering with some tests/large bulk operations) that there was such a large pile of garbage accumulating, that the following code
{code}
VersionGarbageCollector.collectDeletedDocuments
{code}
in the for loop, creates such a large list of NodeDocuments to delete (docIdsToDelete) that it uses up too much memory, causing the JVM's GC to constantly spin in Full-GCs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)