-
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
Kafka scaler | Scale to 0 during Kafka broker replacement even if the fallback is configured #4098
Comments
Hi |
Hi, Thanks for looking into it. Sure, I can provide more, but there is actually nothing else specific. The log is full of information of processing other ScaledObjects of the same kind but for different kafka topics. But it is always the same schema. After the error If the error is Here is a bigger log snippet. I had to replace the clear names:
|
Thanks for the info! |
That might be the problematic part, @sdomme are you willing to fix that part of code and test if it solves your problem? |
I don't have the right skills to contribute in this regards. Sorry. |
Hi there! @sdomme and me are going to have a look at the code and try to fix the problem. Let's see where it goes 😄 |
I have assigned the issue to you to track the work in progress, if you want I can unassign it if you have troubles with the fix |
@theurichde Thx for helping out. |
Report
Hello,
we periodically encounter an issue with some of the ScaledObjects with the Kafka trigger during Kafka broker replacement. Even if we configure the fallback the deployment is scaled to 0. In the case, where I will provide shrinked operator logs for it took approx. 2h for the fallback mechanism to kick in.
Expected Behavior
During faulty Kafka responses, deployment goes to the amount of PODs configured in
fallback.replicas
Actual Behavior
Deployment goes to 0 during Kafka broker replacement and recovers after a long period to the number set in
fallback.replicas
Steps to Reproduce the Problem
Here the ScaledObject we use
Logs from KEDA operator
KEDA Version
2.8.1
Kubernetes Version
1.23
Platform
Amazon Web Services
Scaler Details
Kafka
Anything else?
From this Graph (kube_deployment_status_replicas) you can see the scaling of the Deployment going to 0. The time fits the log I provided.
The text was updated successfully, but these errors were encountered: