[
https://issues.apache.org/jira/browse/KAFKA-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michail resolved KAFKA-13322.
-----------------------------
Resolution: Won't Fix
Having done the analysis the changes required to achieve this are far too
intrusive thus decided not to proceed with this.
> Java client produces a large amount of garbage during a poll
> ------------------------------------------------------------
>
> Key: KAFKA-13322
> URL: https://issues.apache.org/jira/browse/KAFKA-13322
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 3.0.0
> Reporter: Michail
> Priority: Minor
> Labels: new-rebalance-should-fix
>
> The java kafka consumer creates multiple collections during a single poll
> command: in my test system i have a consumer that polls a topic with 100
> partitions and even though no messages are coming through, the code allocates
> around 100M per 5 minutes.
>
> I've investigated the allocations and the biggest ones can be easily avoided
> by moving them to the instance level, something that can be done as
> KafkaConsumer is not thread safe. Purpose of this Jira is to get rid of most
> of them applying either this or a similar approach.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
