[jira] [Updated] (JCR-3983) Possibility to parallelize the Garbage Collection
[ https://issues.apache.org/jira/browse/JCR-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-3983: Fix Version/s: 2.14 > Possibility to parallelize the Garbage Collection > - > > Key: JCR-3983 > URL: https://issues.apache.org/jira/browse/JCR-3983 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-core >Affects Versions: 2.12.1 >Reporter: Claus Köll >Assignee: Claus Köll > Fix For: 2.13.0, 2.14 > > Attachments: JCR-3983.patch > > > We are using jackrabbit as a binary focused repository. We are now in that > situation that the garbage collection runs up to 5 days. To speed up the > process it should be possible to parallelize the mark phase -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JCR-3983) Possibility to parallelize the Garbage Collection
[ https://issues.apache.org/jira/browse/JCR-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Köll updated JCR-3983: Attachment: JCR-3983.patch I think it's ok if we do not modify the DataStoreGarbageCollector Interface. It's really a power user feature. > Possibility to parallelize the Garbage Collection > - > > Key: JCR-3983 > URL: https://issues.apache.org/jira/browse/JCR-3983 > Project: Jackrabbit Content Repository > Issue Type: New Feature > Components: jackrabbit-core >Affects Versions: 2.12.1 >Reporter: Claus Köll >Assignee: Claus Köll > Fix For: 2.13.0 > > Attachments: JCR-3983.patch > > > We are using jackrabbit as a binary focused repository. We are now in that > situation that the garbage collection runs up to 5 days. To speed up the > process it should be possible to parallelize the mark phase -- This message was sent by Atlassian JIRA (v6.3.4#6332)
