You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Shashank Gupta (JIRA)" <ji...@apache.org> on 2014/03/19 07:41:42 UTC
[jira] [Updated] (JCR-3754) [jackrabbit-aws-ext] Add retry logic to
S3 asynchronous failed upload
[ https://issues.apache.org/jira/browse/JCR-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shashank Gupta updated JCR-3754:
--------------------------------
Component/s: jackrabbit-data
Affects Version/s: 2.7.5
Fix Version/s: 2.7.6
> [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload
> ---------------------------------------------------------------------
>
> Key: JCR-3754
> URL: https://issues.apache.org/jira/browse/JCR-3754
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-data
> Affects Versions: 2.7.5
> Reporter: Shashank Gupta
> Fix For: 2.7.6
>
>
> Currently s3 asynchronous uploads are not retried after failure. since failed upload file is served from local cache it doesn't hamper datastore functionality. During next restart all accumulated failed upload files are uploaded to s3 in synchronized manner.
> There should be retry logic for failed s3 asynchronous upload so that failed uploads are not accumulated.
--
This message was sent by Atlassian JIRA
(v6.2#6252)