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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/11/07 04:24:58 UTC

[jira] [Resolved] (OAK-4440) Async upload in S3DataStore can lead to intermittent binary missing exception in cluster

     [ https://issues.apache.org/jira/browse/OAK-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chetan Mehrotra resolved OAK-4440.
----------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 1.6)

> Async upload in S3DataStore can lead to intermittent binary missing exception in cluster
> ----------------------------------------------------------------------------------------
>
>                 Key: OAK-4440
>                 URL: https://issues.apache.org/jira/browse/OAK-4440
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: blob
>            Reporter: Chetan Mehrotra
>
> {{S3DataStore}} supports async upload of binaries. This feature was added to speedup performance for cases where S3 is remote (i.e. Oak/JR2 app was running on premise) (JCR-3733)
> This feature would cause issue in cluster deployment where binaries get uploaded from any cluster node because its possible that binary is not uploaded to S3 (present in local cache of one of the cluster node) and some code in other cluster node tries to read the binary.
> This feature also poses problem in backup and restore where we would need backup the local S3 cache on all the cluster nodes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)