[
https://issues.apache.org/jira/browse/OAK-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656542#comment-15656542
]
Thomas Mueller commented on OAK-4903:
-------------------------------------
Options:
* Don't use a content hash, but instead use a UUID
* Directly stream to S3 (in addition to, or instead of, writing to the local
file system), and "put copy" the S3 entry afterwards to the right file name; if
possible using a channel instead of a stream
* On the client side, wait until the binary is available
* Store those binaries in MongoDB (until they are on S3)
* Chunk binaries so they are not stored in the datastore
* Delay writing the index nodes for some time, until the binaries are on S3
* Use the broadcast cache to distribute binaries
> 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
> Components: blob
> Reporter: Amit Jain
> Assignee: Amit Jain
> Priority: Critical
> Fix For: 1.6
>
>
> 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)
