jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1022) Provide a mechanism to deal with the rate limit in DigitalOcean
Date Tue, 27 Oct 2015 22:42:27 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977299#comment-14977299

ASF subversion and git services commented on JCLOUDS-1022:

Commit 70dba8ebdf710c5f0c8ace07a2fa00d30400d668 in jclouds-labs's branch refs/heads/master
from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=70dba8e ]

JCLOUDS-1022: Automatically handle DigitalOcean rate limit

> Provide a mechanism to deal with the rate limit in DigitalOcean
> ---------------------------------------------------------------
>                 Key: JCLOUDS-1022
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1022
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs
>    Affects Versions: 1.9.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: digitalocean
> The DigitalOcean v2 API is rate limited. The limits are not particularly large, so jclouds
should provide a mechanism to automatically deal with them. See: https://developers.digitalocean.com/documentation/v2/#rate-limit
> Ideally this should be an optional component that users can choose to enable. When enabled,
requests that failed due to the rate limit should be enqueued and retried when the rate limit
resets, and when disabled, requests should fail and a meaningful exception should be propagated.

This message was sent by Atlassian JIRA

View raw message