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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/11/30 11:46:10 UTC
[jira] [Resolved] (OAK-2835) TARMK Cold Standby inefficient cleanup
[ https://issues.apache.org/jira/browse/OAK-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Parvulescu resolved OAK-2835.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.3.12)
resolving as duplicate of OAK-3612
> TARMK Cold Standby inefficient cleanup
> --------------------------------------
>
> Key: OAK-2835
> URL: https://issues.apache.org/jira/browse/OAK-2835
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: segmentmk, tarmk-standby
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Critical
> Labels: compaction, gc, production, resilience
> Attachments: OAK-2835.patch
>
>
> Following OAK-2817, it turns out that patching the data corruption issue revealed an inefficiency of the cleanup method. similar to the online compaction situation, the standby has issues clearing some of the in-memory references to old revisions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)