{"id":59350,"date":"2023-11-09T14:53:38","date_gmt":"2023-11-09T09:23:38","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=59350"},"modified":"2023-11-20T23:03:50","modified_gmt":"2023-11-20T17:33:50","slug":"consumer-rebalancing-in-kafka-an-overview","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/consumer-rebalancing-in-kafka-an-overview\/","title":{"rendered":"Consumer Rebalancing in Kafka- An Overview"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

Apache Kafka is a distributed system consisting of servers and clients that communicate via a high-performance TCP network protocol. We have components generating events (Producers<\/em>) and components that consume those events (Consumers<\/em>). Consumers label themselves with a consumer group name so that each record published on a topic will be delivered to one and only one consumer in the consumer group. We can use this feature to implement load balancing between consumer nodes.<\/p>\n

Consumer Rebalancing<\/strong> in Kafka is a process by which partitions get reassigned among consumers in a group to ensure that each consumer gets an equal number of partitions to process data.<\/p>\n

As a result, Kafka efficiency and effective performance are maintained, thus preventing any overload or underutilization of any consumer.<\/p>\n

Why Consumer rebalancing triggers?<\/strong><\/h2>\n

Consumer rebalancing in Kafka can happen in the following conditions:<\/p>\n

1. A consumer leaves the group<\/p>\n

2. A consumer joins a group<\/p>\n

3. Partitions are added to a topic<\/p>\n

When a consumer experiences a temporary network failure or stays idle for too long, Kafka may consider it a failed consumer and remove it from the group. Meanwhile, Kafka initiates a rebalance to distribute the partitions among the active consumers in the group.<\/p>\n

Let\u2019s take topic T1 with three partitions, a consumer C1, which is the only consumer in group G1, and use it to subscribe to topic T1. Consumer C1 will get all messages from all three partitions.<\/p>\n

\"\"<\/p>\n

If we add two consumers, C2 and C3, to group G1, each consumer will only get messages from a single partition.<\/p>\n

\"\"<\/p>\n

If we add more consumers to this group with a single topic than we have partitions, some of the consumers will be idle and get no messages at all.<\/p>\n

\"\"<\/p>\n

How does Rebalancing work?<\/strong><\/h2>\n

There are two types of rebalancing, depending on the partition assignment strategy that the consumer group uses.<\/p>\n

Eager Rebalancing<\/strong>: Kafka performs eager rebalancing by default, which states that all consumers stop consuming and give up their membership of partitions for a short period. This is also called a “stop the world” event.<\/p>\n

\"\"<\/p>\n

Afterward, Consumer rejoins the group, and reassignment of partitions occurs, this time, there is no guarantee that the consumer will get the same partition as before<\/p>\n

Cooperative Rebalancing<\/strong>: Also referred to as incremental rebalancing. This approach involves reassigning only a small subset of the partitions from one consumer to another and allowing consumers to continue processing records from all the partitions that are not reassigned.<\/p>\n

\"\"<\/p>\n

Conclusion<\/strong><\/h2>\n

Compared to eager, there are clear advantages of using cooperative rebalancing. Kafka consumers who are not concerned by the rebalance can keep processing data without interruptions. So, this algorithm, fortunately, is the default strategy for new Kafka stream applications.<\/p>\n

<\/div>","protected":false},"excerpt":{"rendered":"

Introduction Apache Kafka is a distributed system consisting of servers and clients that communicate via a high-performance TCP network protocol. We have components generating events (Producers) and components that consume those events (Consumers). Consumers label themselves with a consumer group name so that each record published on a topic will be delivered to one and […]<\/p>\n","protected":false},"author":1685,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":345},"categories":[446],"tags":[5550,5549,4844,1604],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/59350"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1685"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=59350"}],"version-history":[{"count":2,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/59350\/revisions"}],"predecessor-version":[{"id":59409,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/59350\/revisions\/59409"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=59350"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=59350"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=59350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}