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

Chetan Mehrotra updated JCR-3754:
---------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Applied the patch in 

# http://svn.apache.org/r1585459
# http://svn.apache.org/r1585460
# http://svn.apache.org/r1585461

> [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
>            Assignee: Chetan Mehrotra
>             Fix For: 2.7.6
>
>         Attachments: JCR-3754.patch, JCR-3754V2.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
(v6.2#6252)

Reply via email to