KEDA ScaledObject not scaling multiple pods when messages arrive in shared RabbitMQ queue #5719
Unanswered
diegolatorre116
asked this question in
Q&A / Need Help
Replies: 1 comment
-
Doing more tests I realized that this actually happens when one of the two instances wakes up very quickly, apparently it consumes the task quickly and the other trigger fails to activate. When limiting resources if both pods were raised. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have the following situation: I have a kubernetes cluster in which I have a Celery application that communicates using RabbitMQ. I have a pod that contains a Celery task but there are 3 different queues for this task:
I need two instances of this pod but each of these with different execution commands, these are the deploys:
First deploy:
Second deploy:
The only thing that changes is the launch command (the --pool which is an irrelevant Celery thing for this example and the queues it is listening to). As you can see, both share the training-forecast-dev queue, and in addition to this, each one has a different one.
So, I also have two ScaledObject:
First Keda:
Second Keda:
Expected behavior
I need that if a task arrives at training-forecast-prefork-dev or training-forecast-prefork-dev the corresponding pod is raised (this is running correctly). I also need that when a task arrives at training-forecast-dev, both pods are raised.
Current behavior
When a task arrives at training-forecast-dev, only one of the pods is raised. I thought that since there were two ScaledObjects, both would be activated and the final result would be the execution of the two pods, but only one ends up being raised even if more than one task arrives at training-forecast-dev.
Beta Was this translation helpful? Give feedback.
All reactions