[
https://issues.apache.org/jira/browse/OAK-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413510#comment-15413510
]
Michael Dürig commented on OAK-4371:
------------------------------------
Maybe we should just lower the log level to info and remove the recommendation
to run checkpoint cleanup here? IMO monitoring the number of checkpoints should
be done from the outside (e.g. through CheckpointMBean in a Sling health
check).
[~dhasler], would the Sling health check be an option here?
> Overly zealous warning about checkpoints on compaction
> -------------------------------------------------------
>
> Key: OAK-4371
> URL: https://issues.apache.org/jira/browse/OAK-4371
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-tar, segmentmk
> Reporter: Michael Dürig
> Labels: compaction, gc, logging
> Fix For: Segment Tar 0.0.12
>
>
> {{FileStore.compact}} logs a warning {{TarMK GC #{}: compaction found {}
> checkpoints, you might need to run checkpoint cleanup}} if there is more than
> a single checkpoints.
> AFIK this is now the norm as async indexing has uses 2 checkpoints
> ([~chetanm], [~edivad] please clarify).
> In any case should we improve this and not hard code any number of expected
> checkpoints. Maybe make the threshold configurable?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
