jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shashank Gupta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCR-3754) [jackrabbit-aws-ext] Add retry logic to S3 asynchronous failed upload
Date Wed, 19 Mar 2014 08:45:43 GMT

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

Shashank Gupta updated JCR-3754:

    Status: Patch Available  (was: Open)

h3. Patch details:
# Add retry logic for failed uploads. Retry count is configurable in S3DataStore configuration
via repository.xml. default value is 3. 
# Used threadpool executer service in S3DataStore#writeAsync instead of spawning new thread
everytime. Threadpool size governed by maxConnections param in aws.properties.
# Exception propagation for failed upload from S3UploadProgressListener to AsyncUploadCallback.
# Defined constants for S3 connection parameters in S3Constants. 

> [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
>         Attachments: JCR-3754.patch
> 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

View raw message