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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2016/07/27 16:08:20 UTC

[jira] [Assigned] (OAK-4138) Decouple revision cleanup from the flush thread

     [ https://issues.apache.org/jira/browse/OAK-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig reassigned OAK-4138:
----------------------------------

    Assignee: Michael Dürig

> Decouple revision cleanup from the flush thread
> -----------------------------------------------
>
>                 Key: OAK-4138
>                 URL: https://issues.apache.org/jira/browse/OAK-4138
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: resilience
>             Fix For: 1.6, Segment Tar 0.0.8
>
>
> I suggest we decouple revision cleanup from the flush thread. With large repositories where cleanup can take several minutes to complete it blocks the flush thread from updating the journal and the persisted head thus resulting in larger then necessary data loss in case of a crash. 
> /cc [~alex.parvulescu]



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