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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/03/20 16:24:43 UTC

[jira] [Commented] (OAK-1341) DocumentNodeStore: Implement revision garbage collection

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

Chetan Mehrotra commented on OAK-1341:
--------------------------------------

Revision GC needs to take into account saved checkpoints (OAK-1586)

> DocumentNodeStore: Implement revision garbage collection
> --------------------------------------------------------
>
>                 Key: OAK-1341
>                 URL: https://issues.apache.org/jira/browse/OAK-1341
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: mongomk
>            Reporter: Thomas Mueller
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 0.20
>
>
> For the MongoMK (as well as for other storage engines that are based on it), garbage collection is most easily implemented by iterating over all documents and removing unused entries (either whole documents, or data within the document). 
> Iteration can be done in parallel (for example one process per shard), and it can be done in any order. 
> The most efficient order is probably the id order; however, it might be better to iterate only over documents that were not changed recently, by using the index on the "_modified" property. That way we don't need to iterate over the whole repository over and over again, but just over those documents that were actually changed.



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