You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (Jira)" <ji...@apache.org> on 2023/06/05 08:25:00 UTC

[jira] [Commented] (OAK-10254) Test cases to reproduce late write inconsistencies

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

Marcel Reutegger commented on OAK-10254:
----------------------------------------

[~stefanegli], the PR is merged, but this issue is still in progress. Can this be resolved?

> Test cases to reproduce late write inconsistencies
> --------------------------------------------------
>
>                 Key: OAK-10254
>                 URL: https://issues.apache.org/jira/browse/OAK-10254
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: documentmk
>            Reporter: Stefan Egli
>            Assignee: Stefan Egli
>            Priority: Major
>
> Test class that reproduces "late-write inconsistencies". These are a type of inconsistencies that can happen if a write manages to be sent to DocumentStore after the lease expired and other instances already did a lastRevRecovery. This is a scenario that can occur if the JVM experiences a stop-the-world JVM-GC for longer than the lease duration (eg 2min)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)