Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KIP-848: The next generation consumer group protocol #912

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

twmb
Copy link
Owner

@twmb twmb commented Feb 20, 2025

This automatically opts into the next gen group if

  • The broker supports it
  • You are using a sticky / cooperative-sticky / range assignor
  • You are not using regex consuming
  • The broker actually supports it (does not reply to the first request with UnsupportedVersion)

This only supports v0 ConsumerGroupHeartbeat at the moment; v1 will come in the next kmsg bump, which will be before v1.19.

twmb added 2 commits February 19, 2025 17:56
* If the rebalance is triggered from the leader noticing a metadata
  update, well, we just noticed it; no need for a metadata update
* Kafka prefers keeping leaders across rebalances
* If we are chosen to be a follower, well, we will update our metadata
  when we are assigned a partition we do not know of
* If we are a leader and are missing a partition, we'll eventually
  notice it and a few minutes later cause a rebalance

This essentially removes a niche optimization in favor of hammering
brokers less with metadata requests.

Also removes some wording from logs in preparation of these same logs
being used in a non-rejoin context.
In prep for consumer group heartbeat request.
Linting on GH is currently broken.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant