You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dmitry Werner (Jira)" <ji...@apache.org> on 2024/07/30 12:27:00 UTC

[jira] [Commented] (KAFKA-17218) kafka-consumer-groups fails to describe all group if one group has been consuming from a deleted topic

    [ https://issues.apache.org/jira/browse/KAFKA-17218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869617#comment-17869617 ] 

Dmitry Werner commented on KAFKA-17218:
---------------------------------------

[~omnia_h_ibrahim] Hello, if you haven't started work yet, can I do?

> kafka-consumer-groups fails to describe all group if one group has been consuming from a deleted topic
> ------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-17218
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17218
>             Project: Kafka
>          Issue Type: Task
>    Affects Versions: 3.6.0, 3.7.0, 3.8.0
>            Reporter: Omnia Ibrahim
>            Assignee: Omnia Ibrahim
>            Priority: Major
>
> `kafka-consumer-groups.sh --describe --all-groups` fails with `org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition.` if single group has metadata for a topic that was recently deleted. 
> As impact this prevent admin from viewing the group metadata for the whole cluster. 
> Instead we should either 
> - follow the same approach when we calculate the lag which print a place holder `-` when it is not applicable to calculate the metadata. 
> - or we exclude instances with deleted topics 
> Currently I am more leaning into the first option with `-` as placeholder.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)