[
https://issues.apache.org/jira/browse/JCR-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453365#comment-15453365
]
Woonsan Ko commented on JCR-3944:
---------------------------------
Hi,
While trying to fix JCR-4008, I provided a pull request, giving an option to
disable AsyncUpload when {{asyncWritePoolSize}} is zero or lower.
Could someone review JCR-4008? I guess that will fix this issue as well.
Thanks in advance,
Woonsan
> 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.3
>
>
> 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)
