-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
KEDA Operator reaching OOM #1565
Comments
Quickly looking at the logs, it is quite strange, on many lines
How many ScaledObjects do you have deployed? And what is this giving you:
|
@zroubalik Hey! |
@avivgold098 sorry, I missed that note 🤦 Could you please enable debug log level? |
Yes :) |
@avivgold098 by chance, isn't there something that could modify the scaledobjects? We shouldn't see that much reconciliation happennig on the scaledobjects |
Have you run that setup with KEDA 2.0? |
@zroubalik Nothing is modified the We experienced the same behavior with |
I have a repro for the issue and I'm looking at it. The frequent reconciliation is odd, but shouldn't cause a memory leak. I had to artificially cause it and can see the memory building up. |
A KEDA operator deployment is suffering from a memory leak, leading to the operator being restarted.
Expected Behavior
Keda operator is able to run with stable memory performance. Memory usage & connections should remain stable over time.
Actual Behavior
Keda operator pod memory is increasing over time until the pod is reached to his memory limit, causing OOM.
Steps to Reproduce the Problem
scaledobjects.keda.sh
kubernetes objectsLogs from KEDA operator - removed objects names
Specifications
Additonal Metrics
Pod performance
The text was updated successfully, but these errors were encountered: