Repository navigation
Add batch consumer partition assignment strategy - #294
Merged
Vruttant1403 merged 4 commits intoOct 12, 2026
Merged
Vruttant1403 merged 4 commits into
Vruttant1403 merged 4 commits into
Conversation
Riya-bhardwaj
force-pushed
the
feature/batch-consumer-partition-assignment-strategy
branch
from
July 21, 2026 04:47
ff20e01 to
16ace08
Compare
Riya-bhardwaj
force-pushed
the
feature/batch-consumer-partition-assignment-strategy
branch
from
October 7, 2026 11:26
cb96be4 to
a2c0ec2
Compare
Vruttant1403
self-requested a review
October 8, 2026 13:29
Vruttant1403
approved these changes
Oct 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Batch consumers use Kafka's default RangeAssignor (eager rebalancing): every rebalance — deploy, restart, or scaling — makes all consumers revoke all partitions before reassigning ("stop-the-world"). There was no supported way to switch to cooperative rebalancing (CooperativeStickyAssignor).
Solution
New opt-in, per-route flag :partition-assignment-strategy. Omit it → unchanged default behavior (no impact on existing consumers). Generic by design — supports any assignor:
:partition-assignment-strategy :cooperative-sticky ; short name
:partition-assignment-strategy "org.apache.kafka.clients.consumer.CooperativeStickyAssignor" ; FQCN
:partition-assignment-strategy [:range :cooperative-sticky] ; ordered preference list (migration)
Short names: :range, :round-robin, :sticky, :cooperative-sticky. Unknown values fail loudly at startup.
Eager → cooperative is protocol-incompatible; do a two-phase rolling deploy: phase 1 [:range :cooperative-sticky], then (after full rollout) phase 2 :cooperative-sticky. New groups can use :cooperative-sticky directly. Runbook in doc/kafka_produce_consume.md.