From notifications-return-33060-apmail-jclouds-notifications-archive=jclouds.apache.org@jclouds.apache.org Tue Oct 27 22:42:29 2015 Return-Path: X-Original-To: apmail-jclouds-notifications-archive@www.apache.org Delivered-To: apmail-jclouds-notifications-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0D9CB18287 for ; Tue, 27 Oct 2015 22:42:29 +0000 (UTC) Received: (qmail 54420 invoked by uid 500); 27 Oct 2015 22:42:28 -0000 Delivered-To: apmail-jclouds-notifications-archive@jclouds.apache.org Received: (qmail 54242 invoked by uid 500); 27 Oct 2015 22:42:28 -0000 Mailing-List: contact notifications-help@jclouds.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jclouds.apache.org Delivered-To: mailing list notifications@jclouds.apache.org Received: (qmail 54198 invoked by uid 99); 27 Oct 2015 22:42:27 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Oct 2015 22:42:27 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CC04E2C1F61 for ; Tue, 27 Oct 2015 22:42:27 +0000 (UTC) Date: Tue, 27 Oct 2015 22:42:27 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: notifications@jclouds.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (JCLOUDS-1022) Provide a mechanism to deal with the rate limit in DigitalOcean MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 (v6.3.4#6332)