jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From José Andrés Cordero Benítez (Jira) <j...@apache.org>
Subject [jira] [Commented] (OAK-9305) Create checkpoint with given revision
Date Wed, 24 Feb 2021 12:33:00 GMT

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

José Andrés Cordero Benítez commented on OAK-9305:

Looks good to me. I have added a suggestion to improve the output of the Bean method, because
at the moment it just shows the revision for which the checkpoint was created, which I think
is not very useful because it is the first argument you send to the method.

However, that depends on how human or machine readable the output should be.

> 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

View raw message