You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Sönke Liebau (Jira)" <ji...@apache.org> on 2020/02/26 16:07:00 UTC
[jira] [Commented] (KAFKA-9609) Memory Leak in Kafka Producer
[ https://issues.apache.org/jira/browse/KAFKA-9609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045652#comment-17045652 ]
Sönke Liebau commented on KAFKA-9609:
-------------------------------------
Is that really a bug though?
If I checked the record-send-total, record-error-total or byte-total metrics for a specific topic I would expect to get the correct number reported no matter how long ago I sent the last record to that topic.
I would say that this works as designed, even though it may not be perfect for your use case.
> Memory Leak in Kafka Producer
> -----------------------------
>
> Key: KAFKA-9609
> URL: https://issues.apache.org/jira/browse/KAFKA-9609
> Project: Kafka
> Issue Type: Bug
> Components: clients, producer
> Affects Versions: 2.4.0
> Reporter: Satish
> Priority: Major
>
> org.apache.kafka.clients.producer.internals.Sender adds Topic Metrics for every topic that we are writing messages to but it never been cleaned up until we close the producer.
> This is an issue if we use single producer and have more number of Dynamic topics (eg: ~ 500 topics per hour) and writing messages to them. As this Metrics map is getting accumulated for every topic, over a period of time we notice the memory usage gets increased gradually.
> It can be easily reproducible by writing messages to the more # of dynamic topics using the same KafkaProducer from apache kafka client libraries or KafkaTemplate from Spring.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)