[ https://issues.apache.org/jira/browse/OAK-2557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352714#comment-14352714 ]
Chetan Mehrotra commented on OAK-2557: -------------------------------------- bq. Is that set becoming too large to cause an OOM Indeed thats the case. The array list had 12M entries taking 3 GB of space. So GC logic should do the deletion in in between > 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 > Priority: Blocker > Fix For: 1.2, 1.0.13 > > > 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)