jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1341) DocumentNodeStore: Implement revision garbage collection
Date Mon, 31 Mar 2014 10:53:15 GMT

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

Chetan Mehrotra commented on OAK-1341:

The required work has been done as per the flow described above. The RevionGC is wired with
the JMX logic and can be invoked. By default the maxAge is set to 1 day. It can be change
by specific config property {{versionGcMaxAgeInSecs}} for DocumentNodeStore

> 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

View raw message