[
https://issues.apache.org/jira/browse/KAFKA-17578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882992#comment-17882992
]
PoAn Yang edited comment on KAFKA-17578 at 9/19/24 12:01 PM:
-------------------------------------------------------------
Hi [~jeffkbkim] and [~dajac], there are 200+ references to TopicMetadata. Do we
want to fully remove partitionRacks? Or we can create a new TopicMetadata
constructor which always set empty partitionRacks to TopicMetadata. And we only
need to change production code and related test cases? Thank you.
was (Author: JIRAUSER300229):
Hi [~jeffkbkim] and [~dajac], there are 200+ references to TopicMetadata. Do we
want to fully remove partitionRacks? Or we can create a new TopicMetadata
constructor which always set empty to TopicMetadata. And we only need to change
production code and related test cases? Thank you.
> Remove partitionRacks from TopicMetadata
> ----------------------------------------
>
> Key: KAFKA-17578
> URL: https://issues.apache.org/jira/browse/KAFKA-17578
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Jeff Kim
> Assignee: PoAn Yang
> Priority: Major
> Labels: kip-848
>
> The ModernGroup#subscribedTopicMetadata takes too much memory due to
> partitionRacks:
> /**
> Map of every partition Id to a set of its rack Ids, if they exist.
> If rack information is unavailable for all partitions, this is an empty map.
> */
> private final Map<Integer, Set<String>> partitionRacks;
>
> This is not being used at the moment as the consumer protocol does not
> support rack aware assignments.
>
> A heap dump from a group with 500 members, 2K subscribed topic partitions
> shows
> 654,400 bytes used for partitionRacks. The rest of the ConsumerGroup object
> holds 822,860 bytes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
