jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7869) Commit queue stuck when input stream of blob blocks
Date Wed, 31 Oct 2018 09:28:00 GMT

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

Marcel Reutegger commented on OAK-7869:

Added an ignored test to trunk: http://svn.apache.org/r1845320

> Commit queue stuck when input stream of blob blocks
> ---------------------------------------------------
>                 Key: OAK-7869
>                 URL: https://issues.apache.org/jira/browse/OAK-7869
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>    Affects Versions: 1.0, 1.2, 1.4, 1.6.0, 1.8.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Major
>             Fix For: 1.10
> This is the same scenario as described in OAK-7867 but for the DocumentNodeStore.
> The behaviour of the DocumentNodeStore is slightly different. The rogue InputStream will
block the CommitQueue inside the DocumentNodeStore and prevent other commits from finishing.
Other commits may proceed up to the point where changes are persisted, including the final
update on the commit root document, but the merge calls for those commits will never return.
> It doesn't look like the issue can cause data loss, but can still affect availability
of the system as other writes are blocked. Writes on other cluster nodes may also be affected
because a blocked CommitQueue means already persisted commits are not propagated through the
background update thread. Commits on other cluster nodes then may conflict because changes
from the affected cluster node are not yet made visible.

This message was sent by Atlassian JIRA

View raw message