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/04/28 11:03:06 UTC

[jira] [Created] (OAK-2817) TARMK Cold Standby cleanup removes too many binary segments

Alex Parvulescu created OAK-2817:
------------------------------------

             Summary: TARMK Cold Standby cleanup removes too many binary segments
                 Key: OAK-2817
                 URL: https://issues.apache.org/jira/browse/OAK-2817
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: segmentmk
    Affects Versions: 1.2.1, 1.1.7, 1.0.12
            Reporter: Alex Parvulescu
            Assignee: Alex Parvulescu
             Fix For: 1.2.2


It looks like the standby cleanup process could remove a lot more binary segments than permitted because of the order in which such segments are persisted. the sync will first persist the data segment referencing a binary, then the binary segment itself, this introduces problems when it spreads over multiple tar files and the #cleanup method expects them to be persisted the other way around (this is an implementation detail of the cleanup, but it is implemented this way for efficiency).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)