-
Notifications
You must be signed in to change notification settings - Fork 599
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
Message Distribution Issues with Kafka brokers: Impact on Pod Scaling #8257
Comments
@naveengogu can you show an example event you're sending to Kafka brokers? also what version are you using? |
@pierDipi I am using version 1.15.2, and this is the sample curl command.
I have deleted the broker, service, and trigger, then redeployed them. Now the messages are being distributed across multiple partitions, but only one pod is consuming all the messages. The pods are not scaling based on events. My containerConcurrency is set to 1. What could be causing the pods not to scale? When I hit the Knative service directly, it scales, but it doesn't scale when I send messages through the brokers. And I found this error in kafka-controller, is it causing that issue?
|
Few more logs
|
Expected Behavior
If I send 9 messages to the Kafka brokers, they should be distributed across 3 partitions in kafka, and 3 pods should scale since I set the concurrency to 1. The pod will just sleep in 10 minutes and print the message
Actual Behavior
When I send a message to the Kafka broker URL, it is being added to a single partition in the Kafka topic. I have 3 partitions, but because of this, my pods are not scaling to more than one, based on the messages.
The text was updated successfully, but these errors were encountered: