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 2014/03/17 16:08:01 UTC

[jira] [Commented] (OAK-1158) MVCC old revision cleanup

    [ https://issues.apache.org/jira/browse/OAK-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937897#comment-13937897 ] 

Michael Dürig commented on OAK-1158:
------------------------------------

For unifying management of various backends (e.g. OAK-1160), would it make sense to add a {{GarbageCollectableNodeStore}} interface like we have for the blob store (i.e. {{GarbageCollectableBlobStore}})? [~jukkaz] WDYT wrt. OAK-631, [~chetanm] WDYT wrt. OAK-1341?

> MVCC old revision cleanup
> -------------------------
>
>                 Key: OAK-1158
>                 URL: https://issues.apache.org/jira/browse/OAK-1158
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: mk
>            Reporter: Michael Marth
>            Assignee: Michael Marth
>
> Opening this issue as OAK-114 seems mainly concerned with finding the right retention time.
> We need a way to clean up old MVCC revisions in order to keep the repo from growing indefinitely.
> Ideally, this could be done independently of the MK impl, otherwise we need it for TarMK and MongoMK



--
This message was sent by Atlassian JIRA
(v6.2#6252)