[
https://issues.apache.org/jira/browse/OAK-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937908#comment-13937908
]
Jukka Zitting commented on OAK-1158:
------------------------------------
I'd rather put such functionality in a clearly separate {{NodeStoreMBean}}
management interface that's made accessible through JMX. The interface can be
extended to things like {{SegmentNodeStoreMBean}} and
{{DocumentNodeStoreMBean}} to expose more details of each backend.
> 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)
