-
Notifications
You must be signed in to change notification settings - Fork 747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMQP Gateway rate limit #353
Comments
I may be wrong, but for option 1, you can take a look at |
@VaibhavPage yes I've looked at parallelism, but, correct me if I'm wrong, it doesn't prevent the maximum simultaneous execution of workflows, but only steps (pods?) within a workflow |
My bad, you are right. |
dgrisonnet
added a commit
to dgrisonnet/argo-events
that referenced
this issue
Oct 15, 2019
Signed-off-by: Damien Grisonnet <[email protected]>
dgrisonnet
added a commit
to dgrisonnet/argo-events
that referenced
this issue
Oct 15, 2019
Signed-off-by: Damien Grisonnet <[email protected]>
dgrisonnet
added a commit
to dgrisonnet/argo-events
that referenced
this issue
Oct 16, 2019
Signed-off-by: Damien Grisonnet <[email protected]>
VaibhavPage
pushed a commit
that referenced
this issue
Oct 21, 2019
* Add rateLimit option to amqp gateway (#353) Signed-off-by: Damien Grisonnet <[email protected]> * Add ratePeriod option to amqp gateway Signed-off-by: Damien Grisonnet <[email protected]> * Fix period value Signed-off-by: Damien Grisonnet <[email protected]> * Fix errors import to keep the codebase consistent Signed-off-by: Damien Grisonnet <[email protected]>
Closing it as #378 got merged |
juliev0
pushed a commit
to juliev0/argo-events
that referenced
this issue
Mar 29, 2022
* Add rateLimit option to amqp gateway (argoproj#353) Signed-off-by: Damien Grisonnet <[email protected]> * Add ratePeriod option to amqp gateway Signed-off-by: Damien Grisonnet <[email protected]> * Fix period value Signed-off-by: Damien Grisonnet <[email protected]> * Fix errors import to keep the codebase consistent Signed-off-by: Damien Grisonnet <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In the project I'm using argo in, I often get a batch of ~800events sent by an application I can't easily modify. The problem is that our Kubernetes cluster isn't able to handle all of these events simultaneously, but the Argo AMQP Gateway doesn't have to logic to determine the maximum number of events it may grab. Therefore, it fetches all messages available on rabbitmq, and indirectly kills our cluster with heavy load.
I thought of limiting the number of pod in the cluster with Kubernetes, but all exceeding events leads to a failure.
Describe the solution you'd like
To this problem, I reckon 2 available solutions :
Describe alternatives you've considered
The options I've thought of were;
Additional context
/
The text was updated successfully, but these errors were encountered: