Skip to content

Conversation

@ThomasCAI-mlv
Copy link
Collaborator

@ThomasCAI-mlv ThomasCAI-mlv commented Nov 28, 2025

Rootcause
In Kafka 4 adminClient, AdminClient.describeConsumerGroups(groupIds).all() would complete exceptionally when given at least one non-existing groupId in groupIds, throwing an ExecutionException (GroupIdNotFoundException).
This error was not handled as it would complete normally with a DEAD group prior to the KIP1043.

Implementation

  • Added a try-catch block to handle the ExecutionException, and returning an EMPTY group state.
  • Then it is no longer possible to get a DEAD group state (TBC), but it is kept for retro compatibility with Kafka server 3.X
  • Added more precision to the "Reset-offset" error message, as the consumer group will be considered DEAD after the time defined by session.timeout.ms (as mentioned in Apache Kafka)

@ThomasCAI-mlv ThomasCAI-mlv self-assigned this Nov 28, 2025
@ThomasCAI-mlv ThomasCAI-mlv added the bug Something isn't working label Nov 28, 2025
@ThomasCAI-mlv ThomasCAI-mlv linked an issue Nov 28, 2025 that may be closed by this pull request
@sonarqubecloud
Copy link

sonarqubecloud bot commented Dec 3, 2025

@loicgreffier loicgreffier merged commit 4ef4ec0 into master Dec 3, 2025
4 checks passed
@loicgreffier loicgreffier deleted the feat/fix-reset-offset branch December 3, 2025 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reset-offset doesn't create consumer group

3 participants