You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/02/09 16:13:18 UTC

[jira] [Updated] (JCR-3944) CachingDataStore - Disable AsyncUploadCache

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

Davide Giannella updated JCR-3944:
----------------------------------
    Fix Version/s:     (was: 2.11.4)
                   2.13.0

> CachingDataStore - Disable AsyncUploadCache
> -------------------------------------------
>
>                 Key: JCR-3944
>                 URL: https://issues.apache.org/jira/browse/JCR-3944
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-data
>            Reporter: Amit Jain
>            Priority: Critical
>             Fix For: 2.13.0
>
>
> Enabling AsyncUploadCache can lead to data inconsistencies. When a node is created the {{CachingDataStore#addRecord}} call returns immediately with the blob id, while corresponding blob is uploaded asynchronously. This can cause the inconsistency as if there is an error in the upload the node is already created.
> Also, this may not be visible immediately and it will be very hard to discern the root cause.
> AsyncUploadCache is enabled by default with value set to 100 and should be disabled by default by setting to 0.



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