[
https://issues.apache.org/jira/browse/OAK-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604643#comment-15604643
]
Michael Marth commented on OAK-4903:
------------------------------------
IIUC the missing binary problem occurs in deployments where both, the DS (S3)
*and* the node store (e.g. Mongo or RDB), are shared. If so:
how about using Mongo (or RDB) as a shared cache while the upload is in
progress?
> Async uploads in S3 causes issues in a cluster
> ----------------------------------------------
>
> Key: OAK-4903
> URL: https://issues.apache.org/jira/browse/OAK-4903
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: Amit Jain
> Assignee: Amit Jain
> Priority: Critical
>
> S3DataStore and CachingFDS through the CachingDataStore enable async uploads.
> This causes problems in clustered setups where uploads can sometimes be
> visible after a delay. During this time any request for the corresponding
> asset/file would return errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
