[
https://issues.apache.org/jira/browse/KAFKA-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-20680:
------------------------------------
Component/s: group-coordinator
streams
> Prevent stale revocation state when Streams static member temporarily leaves
> ----------------------------------------------------------------------------
>
> Key: KAFKA-20680
> URL: https://issues.apache.org/jira/browse/KAFKA-20680
> Project: Kafka
> Issue Type: Improvement
> Components: group-coordinator, streams
> Reporter: sanghyeok An
> Assignee: sanghyeok An
> Priority: Minor
>
> A static member leaving with epoch -2 may later be replaced with a new member
> id for the same instance id. Since we clear the pending revocations and reset
> the assigned task epochs for that replacement, keeping the member in
> UNREVOKED_TASKS would leave an inconsistent state: there are no pending
> revocations left to acknowledge, but reconciliation would still treat the
> member as waiting for revocation acknowledgement. Move it back to STABLE so
> the rejoining static member can be reconciled from the reset assignment.
> More details are available here
> https://github.com/apache/kafka/pull/22245#discussion_r3381004665
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
