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 2017/12/13 07:20:00 UTC

[jira] [Resolved] (OAK-7053) Commit fails even though change made it to the DocumentStore

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

Marcel Reutegger resolved OAK-7053.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.13

Fixed in trunk: http://svn.apache.org/r1817977

> Commit fails even though change made it to the DocumentStore
> ------------------------------------------------------------
>
>                 Key: OAK-7053
>                 URL: https://issues.apache.org/jira/browse/OAK-7053
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: documentmk
>    Affects Versions: 1.7.9
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Critical
>             Fix For: 1.7.13, 1.8
>
>
> This is the same as OAK-3903, but for the new code path introduced with OAK-5788. The DocumentNodeStore will consider a commit as failed even though the changes were applied to the DocumentStore, but then the response fails e.g. because of a communication error or a crash of the MongoDB primary.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)