[
https://issues.apache.org/jira/browse/OAK-10526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823224#comment-17823224
]
Julian Reschke commented on OAK-10526:
--------------------------------------
trunk:
[6c3b65812f|https://github.com/apache/jackrabbit-oak/commit/6c3b65812fa0a7088b353488e0219c93f3dde30b]
(1.60.0)
[e73cb97510|https://github.com/apache/jackrabbit-oak/commit/e73cb9751072a5733d3045c8f1ffd42405a663e5]
[5be575223d|https://github.com/apache/jackrabbit-oak/commit/5be575223d2f60470e795ffb10a78520f76195cb]
[9f8b7d8502|https://github.com/apache/jackrabbit-oak/commit/9f8b7d8502e2e61c74d6d593e831bd2b5ced5a3f]
> split doc can contain still referenced revisions without _sdMaxRevTime
> indicating so
> ------------------------------------------------------------------------------------
>
> Key: OAK-10526
> URL: https://issues.apache.org/jira/browse/OAK-10526
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
> Affects Versions: 1.58.0
> Reporter: Stefan Egli
> Assignee: Stefan Egli
> Priority: Major
> Fix For: 1.60.0
>
>
> When a document grows too large, part of it is split into previous documents.
> Those also called split documents are marked with _sdMaxRevTime reflecting
> the newest (max) revision timestamp the document contains. GC later can
> delete split documents where _sdMaxRevTime is older than 24h or any existing
> checkpoint. This is based on the assumption that _sdMaxRevTime can be
> compared to "older than 24h or any existing checkpoint" - while _sdMaxRevTime
> only indicates the newest revision contained within. There can thus be a
> situation when a split document contains a revision that is still referenced
> by a current (not older than 24h) head revision or a checkpoint - but
> _sdMaxRevTime is old enough for GC to remove that split doc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
