You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/05/29 22:16:20 UTC

[jira] [Assigned] (JCLOUDS-100) Better handling of API rate limits

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

Andrew Bayer reassigned JCLOUDS-100:
------------------------------------

    Assignee: Andrew Bayer
    
> Better handling of API rate limits
> ----------------------------------
>
>                 Key: JCLOUDS-100
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-100
>             Project: jclouds
>          Issue Type: Bug
>    Affects Versions: 1.5.10
>            Reporter: Omar Alrubaiyan
>            Assignee: Andrew Bayer
>            Priority: Critical
>
> Right now it seems that there is some retry logic when API operations fail. However, the retry logic does not handle hitting the API rate limit very well. The problem is that the retries are done successively instead of  exponential back-off retries which is the recommended way of dealing with EC2 API limits.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira