[
https://issues.apache.org/jira/browse/OAK-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656683#comment-15656683
]
Chetan Mehrotra commented on OAK-4903:
--------------------------------------
Another possible option
Have a new method in BlobStore where one can pass options. There we can provide
setting like write synchronously to backend. FileDataStore would just ignore
the option while S3DataStore would by pass cache and write the stream to S3
itself.
{code}
String writeBlob(InputStream in, BinaryOptions options)
{code}
Then LuceneIndexEditor would use this method directly instead of method exposed
on NodeStore. Later for 1.8 we can look into exposing this to JCR layer
> 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)
