You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/07/19 12:07:04 UTC
[jira] [Commented] (LIBCLOUD-360) Implement retry logic
[ https://issues.apache.org/jira/browse/LIBCLOUD-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632763#comment-14632763 ]
ASF GitHub Bot commented on LIBCLOUD-360:
-----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/libcloud/pull/515
> Implement retry logic
> ---------------------
>
> Key: LIBCLOUD-360
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-360
> Project: Libcloud
> Issue Type: Improvement
> Components: Storage
> Reporter: Ben McCann
>
> I'd frequently upload 100GB+ files to OpenStack object storage (Swift), but have run into trouble with tools that don't retry as it can be tough to do such a large transfer without any network hiccup. I'm currently using the official python-swiftclient since it has retry logic (see https://github.com/openstack/python-swiftclient/blob/master/swiftclient/client.py), but I like that libcloud works with other providers such as S3 and Azure as well. The python-swiftclient has an exponential backoff where it sleeps first 1 second, then 2, then 4, up to a max of 64 seconds between retries (1 and 64 are the min and max, but are configurable). It would be great to see a similar logic in libcloud.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)