Per-Partition Fair Processing#1614
Open
cavus700 wants to merge 1 commit into
Open
Conversation
cavus700
force-pushed
the
kafka-per-partition-fair-processing
branch
from
bea02ab to
d5f221e
Compare
cavus700
force-pushed
the
kafka-per-partition-fair-processing
branch
from
d5f221e to
950b855
Compare
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
1 participant
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.
Breaking Changes
Added
Per-partition fair processing: The Kafka consumer now processes partitions independently. Each assigned partition gets its PartitionProcessor, preventing a single busy or slow partition from starving others. This ensures equal processing throughput across all partitions.
Kafka Pause/Resume back-pressure: When a partition's processing channel is full, the consumer pauses fetching from that partition. This allows other partitions to continue being consumed without blocking the main consume loop.
Partition rebalance handling: The consumer now registers SetPartitionsAssignedHandler and SetPartitionsRevokedHandler callbacks. On assignment, a per-partition processor is created. On revocation, completed in-flight messages are drained and offsets are committed before the partition is released.
Round-robin commit loop: The commit loop polls all partition processors in round-robin fashion, picking up completed tasks from each partition's channel. This gives each partition equal attention for offset storage and commits.
New log events: PartitionAssigned, PartitionRevoked, PartitionPaused, PartitionResumed for observability into partition lifecycle and back-pressure behavior.