[JCR-3944] CachingDataStore - Disable AsyncUploadCache

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Component/s: jackrabbit-data
• Assignee: Unassigned
• Reporter: Amit Jain
• Created: 15/Jan/16 11:14
• Updated: 18/Dec/19 12:38
• Resolved: 10/Nov/16 10:55

Description

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.

Issue Links

• relates to: JCR-3943 [jackrabbi-aws-ext] Data inconsistency due to race condition during async uploads
• relates to: JCR-4008 Restore TestCachingFDS.testDeleteRecord() to fix it with disabling AsyncUpload in unit tests