jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (OAK-8300) Revision GC may remove previous document without removing reference
Date Tue, 11 Jun 2019 10:52:13 GMT

     [ https://issues.apache.org/jira/browse/OAK-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Davide Giannella closed OAK-8300.

bulk close 1.14.0

> Revision GC may remove previous document without removing reference
> -------------------------------------------------------------------
>                 Key: OAK-8300
>                 URL: https://issues.apache.org/jira/browse/OAK-8300
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>    Affects Versions: 1.12.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.14.0
> Depending on timing it may happen that the Revision GC removes a previous document without
updating the main document. This can only happen in a cluster when modifications to a document
happen on one cluster node and the Revision GC runs on the other cluster node. Updating the
main document on Revision GC fails when the document was split after a background update that
contained the latest change on the document and the document is not updated anymore. On the
cluster node where the Revision GC runs, the document may then stay in the cache in a state
that doesn't reflect the split. When the Revision GC runs, the main document from the cache
will not show the reference to the previous document.
> The Revision GC will print a log message that says like:
> {noformat}
> Split document 4:p/content/foo/r169f074b41f-0-1/0 for path p/content/foo/r169f074b41f-0-1/0
not referenced anymore. Main document is 2:/content/foo
> {noformat}

This message was sent by Atlassian JIRA

View raw message