[
https://issues.apache.org/jira/browse/KAFKA-21182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-21182:
------------------------------------
Component/s: admin
streams
> StreamsGroupDescribe does not return tasks pending revocation
> -------------------------------------------------------------
>
> Key: KAFKA-21182
> URL: https://issues.apache.org/jira/browse/KAFKA-21182
> Project: Kafka
> Issue Type: Bug
> Components: admin, streams
> Reporter: sanghyeok An
> Assignee: sanghyeok An
> Priority: Minor
> Labels: streams
>
> The Assignment field in StreamsGroupDescribe currently includes only
> assignedTasks, excluding tasks in tasksPendingRevocation. However, the
> coordinator still considers the member responsible for these tasks until
> revocation is acknowledged.
> When an active task moves from member A to member B, it can therefore
> disappear from both members’ current assignments in the Describe response: A
> is still pending revocation, while B cannot receive the task until A releases
> it. This makes it difficult to identify which member is holding up the
> transfer.
> The same issue was fixed for consumer groups in KAFKA-20431. We should
> similarly include tasks pending revocation in the assignment returned by
> StreamsGroupDescribe, covering active, standby, and warm-up tasks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
