[
https://issues.apache.org/jira/browse/KAFKA-16933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lianet Magrans updated KAFKA-16933:
-----------------------------------
Fix Version/s: 3.8.0
> New consumer leave group flow may not send leave request and clear epoch
> ------------------------------------------------------------------------
>
> Key: KAFKA-16933
> URL: https://issues.apache.org/jira/browse/KAFKA-16933
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Major
> Labels: kip-848-client-support
> Fix For: 3.8.0
>
>
> When leaving a group (due to close or unsubscribe), the consumer needs to run
> revocation callbacks. In the case where this callbacks fail (user error or
> timeout due to long running callback), the consumer should still clear its
> epoch and send a leave group heartbeat. This is currently the case for
> unsubscribe but not for close, so should be fixed.
> Also note that clearing the epoch even if the callback fails is needed to
> ensure that the last epoch is not used anymore in offset commit requests
> after the member leaves the group (ex. when auto-commit enabled).
> Also note that this should still be applied (clear epoch) if a member that is
> running the callbacks to leave get fenced. It does not need to send the leave
> group request but should take all leaving action to leave the client in a
> consistent state (avoiding auto-commits that could happen while it leaves,
> that would use the fenced epoch)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
