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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2014/11/20 13:35:33 UTC

[jira] [Comment Edited] (OAK-2267) Expose checkpoints through JMX

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

Marcel Reutegger edited comment on OAK-2267 at 11/20/14 12:34 PM:
------------------------------------------------------------------

There are some copy/past leftovers from the SegmentCheckpointMBean and the created date is available from the checkpoint revision. See updated patch.

Would it make sense to reduce some of the duplicate code in the two MBean implementations?


was (Author: mreutegg):
There are some copy/past leftovers from the SegmentCheckpointMBean and the created date is available from the checkpoint revision. See updated patch.

Would it make sense to reduce some of the duplicate code in he two MBean implementations?

> Expose checkpoints through JMX
> ------------------------------
>
>                 Key: OAK-2267
>                 URL: https://issues.apache.org/jira/browse/OAK-2267
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>             Fix For: 1.1.3
>
>         Attachments: OAK-2267-doc.patch, OAK-2267-doc.patch, OAK-2267.patch
>
>
> Revision clean works best when stale checkpoints have been removed. Currently the repository has to be taken offline for this. 
> I suggest we expose Oak's checkpoint functionality via JMX, making it possible to list, create and delete checkpoints. 



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