jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-3617) RDBDocumentStore: improve retry logic in updateDocument
Date Wed, 11 Nov 2015 16:12:11 GMT

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

Julian Reschke updated OAK-3617:
--------------------------------
    Attachment: OAK-3617.diff

Test case for measuring concurrent updates, plus an attempt to improve the RDBDocumentStore,
however test results aren't really conclusive yet.

> 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
>         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)

Mime
View raw message