If Kafka allows groups to have the same name, the offset tracking for a partition would get out of whack because a consumer in group 1 would overwrite the offset of a consumer in group 2 (and vice versa). This is a good example showcasing why we cannot have two or more consumer groups ( group.ids) with the same name. Either employed by a production company or working independently, producers plan and coordinate various aspects of film production, such as selecting the script, coordinating writing, directing, editing, and arranging financing. In group 1, each consumer just reads from one partition. A film producer is a person who oversees film production. Both consumers in group 2 read from two partitions each. Group 1 holds four consumers (maxed out), while group 2 holds two consumers (space for 2 more consumers). A twenty year veteran of the music business, Cliff Goldmacher is an engineer, producer, musician and owner of recording studios in Nashville and New York City. Topic T1 has four partitions, and two consumer groups exist, group 1 and group 2. If you don't define a consumer.id, the Kafka client (Java, Python, Node.js, etc) usually chooses a random ID.Īnother good example to understand the relationship between group.id and consumer.id is the following figure: consumer.ids) because the topic has four partitions.Įach consumer has a unique consumer.id across its consumer group. We can have a maximum of four consumers (i.e. Each ID (or name) of a consumer represents the consumer.id. Here we have four partitions and three consumers joined the consumer group: Consumer 0, Consumer 1 and Consumer 2. A consumer group can have one or multiple consumers, but only as many consumers as partitions are available in the topic. of La Bohme and A Midsummer Nights Dream, and his wife and collaborative partner. Your group.id always represents a unique name/ID of your consumer group across your Kafka cluster. producers, organizations, awards, film credits, and terminology. Consumer 0 and consumer 2 read from one partition each, whereas consumer 1 reads from two partitions. In this example, we have one topic with four partitions, one consumer group and three consumers inside the consumer group. The figure below describes the difference between group.id and consumer.id really well.

Foilmcompanion poducer