-
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
SIGSEGV crash in RequestScale #4557
Comments
Updating to version 2.10.1 to check if it will help |
With version 2.10.1 it works without crash for a week already. |
@zroubalik are you certain that both #4413 and #4389 are fixed in 2.10.1 ? why isn't there a matching PR on them which shows the fix and why are they still opened ? |
No these ^^ are not fixed yet. I belive the issue described here has been fixed in 2.10.1 |
Closing this issue. Keda pods are up for 11 days without crash |
Report
Keda crashes in the middle of the operations
Expected Behavior
Not to crash and continue operations
Actual Behavior
Crash with panic: runtime error: invalid memory address or nil pointer dereference
Steps to Reproduce the Problem
Can't reproduce, it happens in the middle of the regular operations.
Will try to find and correlations.
We have 3 EKS clusters with Keda. And Keda crashes only in the biggest cluster (with 1700 pods).
Logs from KEDA operator
KEDA Version
2.10.0
Kubernetes Version
1.24
Platform
Amazon Web Services
Scaler Details
CPU, Memory, Kafka, RabbitMQ
Anything else?
No response
The text was updated successfully, but these errors were encountered: