You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the scaled job description (for triggers redis / mongodb and probably more) I'm seeing this log -
Even though scaler is built and jobs are starting correctly.
My hunch is that it happens when more than one scaler is defined in the same deployment.
Probably not urgent but should be checked.
Expected Behavior
No warnings in scaler description if it's built correctly.
Actual Behavior
Warning logs are present.
Steps to Reproduce the Problem
Try to define two redis scalers in same deployment
Thanks for reporting, we are aware of this problem. It is related to the caching problem, we discussed on the last community call, related to this: #5926 #6176
In this specific usecase we KEDA was able to recover, you can ignore these warnings. We are working towards finding a proper solution.
Report
In the scaled job description (for triggers redis / mongodb and probably more) I'm seeing this log -
Even though scaler is built and jobs are starting correctly.
My hunch is that it happens when more than one scaler is defined in the same deployment.
Probably not urgent but should be checked.
Expected Behavior
No warnings in scaler description if it's built correctly.
Actual Behavior
Warning logs are present.
Steps to Reproduce the Problem
:scaledjobs
> scaler description)Logs from KEDA operator
KEDA Version
2.15.0
Kubernetes Version
1.28
Platform
Google Cloud
Scaler Details
Redis
Anything else?
No response
The text was updated successfully, but these errors were encountered: