You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2016/10/25 05:21:58 UTC

[jira] [Commented] (OAK-4903) Async uploads in S3 causes issues in a cluster

    [ https://issues.apache.org/jira/browse/OAK-4903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604240#comment-15604240 ] 

Amit Jain commented on OAK-4903:
--------------------------------

Most problems are because of lucene blobs not available on secondary nodes where the index would lag continually and would causes them to report a missing blobs continuously.
Specifically, for lucene we might consider:
* OAK-3140 - And use special handling to always do sync uploads for lucene
* Adding a special stream to be used which would always cause do sync uploads

cc/ [~chetanm], [~tmueller]

> 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)