Scaled Job behaviour with Redis Trigger not plausible #1328
Unanswered
QuintinBecker
asked this question in
Q&A / Need Help
Replies: 2 comments
-
@TsuyoshiUshio PTAL^ |
Beta Was this translation helpful? Give feedback.
0 replies
-
Could you share your log and find this log? The behavior is similar to "default" strategy. If the log shows following, it is surely accurate strategy is selected. If so, we need to investigate deeper, it also helpful to get the log.
https://github.com/kedacore/keda/blob/main/pkg/scaling/executor/scale_jobs.go#L286-L308 |
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
-
We use ScaledJobs for long running workloads.
At the moment we write events to the Redis-List we can see some jobs getting scheduled, but much less than we would expect.
In addition there are some entries in the list that stay there for very long time and cause a very delayed scaleup.
During this delay we see following output in KEDA-Operator:
Please correct me but what I see is that there are 32 running jobs and two elements waiting in the Redis-List. As our maxReplicaCount is set to 100 there should be some new jobs to be scaled.
What am I missing here ?
This is the definition of the ScaledJob:
Beta Was this translation helpful? Give feedback.
All reactions