Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 27C59200BC2 for ; Thu, 17 Nov 2016 13:21:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 26866160B0B; Thu, 17 Nov 2016 12:21:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DCBE4160AFF for ; Thu, 17 Nov 2016 13:20:59 +0100 (CET) Received: (qmail 44205 invoked by uid 500); 17 Nov 2016 12:20:59 -0000 Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@brooklyn.apache.org Delivered-To: mailing list dev@brooklyn.apache.org Received: (qmail 44157 invoked by uid 99); 17 Nov 2016 12:20:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Nov 2016 12:20:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EB2002C0059 for ; Thu, 17 Nov 2016 12:20:58 +0000 (UTC) Date: Thu, 17 Nov 2016 12:20:58 +0000 (UTC) From: "Svetoslav Neykov (JIRA)" To: dev@brooklyn.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (BROOKLYN-394) "Request limit exceeded" on Amazon MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 17 Nov 2016 12:21:01 -0000 Svetoslav Neykov created BROOKLYN-394: ----------------------------------------- Summary: "Request limit exceeded" on Amazon Key: BROOKLYN-394 URL: https://issues.apache.org/jira/browse/BROOKLYN-394 Project: Brooklyn Issue Type: Bug Reporter: Svetoslav Neykov Any moderately sized blueprint could trigger {{Request limit exceeded}} on Amazon (say kubernetes). The only way users have control over the request rate is by setting {{maxConcurrentMachineCreations}} with the current recommended value of 3 (see clocker.io). It's bad user experience if one needs to adapt the location based on the blueprint. Possible steps to improve: * Add to troubleshooting documentation * Make maxConcurrentMachineCreations default to 3 * Check are we polling for machine creation too often. * Check how many requests are we hitting Amazon with (per created machine) * The number of requests per machine could vary from blueprint to blueprint (say if the blueprint is creating security networks, using other amazon services). Is there a way to throttle our requests to amazon and stay below a certain limit per second? Some docs on rate limits at http://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html. -- This message was sent by Atlassian JIRA (v6.3.4#6332)