[jira] [Commented] (OAK-9305) Create checkpoint with given revision

["Marcel Reutegger (Jira)" <ji...@apache.org>]

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

Marcel Reutegger commented on OAK-9305:
---------------------------------------

bq.  I was wondering if and how that could be improved.

[~stefanegli], I agree and I also don't quite like it. Instead of adding those properties, the method on the bean could provide a way to specify them. Then it would be up to the user to decide what to add. But then I don't know if JMX clients are even able to handle complex input types like a Map.

> Create checkpoint with given revision
> -------------------------------------
>
>                 Key: OAK-9305
>                 URL: https://issues.apache.org/jira/browse/OAK-9305
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>         Attachments: OAK-9305-create-checkpoint-with-given-revision.patch, OAK-9305.patch
>
>
> Checkpoints are used by async index updates to keep track of what has already been indexed. When such a checkpoint is removed, either by accident or due to an issue in the code, the async index update needs to create indexes from scratch. Depending on the size of the repository this can be an expensive and long running operation. At least for the DocumentNodeStore it is theoretically possible to create a checkpoint retroactively up to the point where the revision garbage collector cleans up old changes. By default this is 24 hours.
> This improvement is about adding a method to the DocumentNodeStoreMBean that allows a user to create a checkpoint with a given revision and lifetime.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)