[
https://issues.apache.org/jira/browse/OAK-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15818049#comment-15818049
]
Alex Parvulescu commented on OAK-5416:
--------------------------------------
bq. In that case the checkpoint would be left.
that would not be the only problem though. {{async}} property would also be
left, which means the sync property index would never be updated. the only way
to recover would be to remove the property and a full reindex, adding a manual
checkpoint cleanup to this doesn't sound that much worse. but on the other hand
providing this cleanup method would give the false sense o security that
everything is ok, when it really isn't (see point about reindexing earlier).
> Async reindex of a sync property does't release created checkpoint
> ------------------------------------------------------------------
>
> Key: OAK-5416
> URL: https://issues.apache.org/jira/browse/OAK-5416
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Alex Parvulescu
> Assignee: Alex Parvulescu
> Priority: Minor
> Fix For: 1.5.18
>
> Attachments: OAK-5416-v2.patch, OAK-5416-v3.patch, OAK-5416.patch
>
>
> Async reindex of a property index creates a checkpoint to use as a reference,
> but it fails to clean it up when done. In the usual reindexing scenario the
> async indexer needs to keep the created checkpoint as a reference for
> subsequent runs, but this is a 'one off' case, so cleanup of this reference
> checkpoint must also happen at the end of the cycle.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
