Multiple Pod Replicas Connecting to the same Kafka Topic and Group?

Hi all,

I have an app that I’ve deployed to a Kubernetes cluster, the app connects to a Kafka instance and reads messages from 1 specific group and 1 topic.

I want to have this a bit more resistant and I want to increase the number of replicas in Kubernetes and set it to 3 or 5 for example.

But I’m not sure if this is going to be OK for the Kafka messages… has anyone done this before and did you have any issues having multiple pod replicas connecting to the same Kafka topic?

Any suggestions would be appreciated!


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I think these points in the documentation are pretty helpful:

I also found the following quote here:

If you create multiple consumer instances using the same group ID, they’ll load balance reading from the topic.

Still, even if the system you’re using supports your requirements, you might be accidentally misconfiguring it or something like that. So I highly recommend testing your code as much as possible.

Caveat: I don’t have too much experience with Kafka, so better to double check what I’m about to say.

My understanding is that Kafka is specifically designed for this particular scenario. Multiple clients can add messages and multiple clients can consume them.