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 "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/11/13 13:37:10 UTC

[jira] [Resolved] (OAK-3617) RDBDocumentStore: improve retry logic in updateDocument

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

Julian Reschke resolved OAK-3617.
---------------------------------
    Resolution: Fixed

trunk: http://svn.apache.org/r1714034
1.2: http://svn.apache.org/r1714187
1.0: http://svn.apache.org/r1714198

> RDBDocumentStore: improve retry logic in updateDocument
> -------------------------------------------------------
>
>                 Key: OAK-3617
>                 URL: https://issues.apache.org/jira/browse/OAK-3617
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: rdbmk
>    Affects Versions: 1.3.9, 1.2.7, 1.0.23
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 1.3.11, 1.2.8, 1.0.24
>
>         Attachments: OAK-3617.diff
>
>
> updateDocument currently attempts to update the document using a String append operation, and if that fails it will retry with a full rewrite.
> However, these operations may be conditional on the previous value of MODCOUNT. If this is the case, and the append did not fail with an SQLException, we know that a full rewrite isn't going to work either, thus we can skip the attempt (thus, the outer retry logic will need to refetch the document from storage before retrying).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)