libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-360) Implement retry logic
Date Wed, 13 May 2015 15:49:00 GMT


ASF GitHub Bot commented on LIBCLOUD-360:

GitHub user arpithkp opened a pull request:

    [LIBCLOUD-360] [LIBCLOUD-709] Retry on rate limit and connection timeout.

    [Retry Logic](
    [Rate Limit Logic](

You can merge this pull request into a Git repository by running:

    $ git pull retry_rate_limit

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #515
commit 38158c8e67d3539fb8aa619adc6b726479153955
Author: Arpith Kuppur Prakash <>
Date:   2015-05-06T19:02:17Z

    [LIBCLOUD-360] [LIBCLOUD-709] Retry on rate limit and connection timeout.


> Implement retry logic
> ---------------------
>                 Key: LIBCLOUD-360
>                 URL:
>             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,
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

View raw message