kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-3892) Clients retain metadata for non-subscribed topics
Date Wed, 22 Jun 2016 20:39:16 GMT

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

Ismael Juma commented on KAFKA-3892:
------------------------------------

I was explaining a known cause of it happening. :) The protocol did not support a metadata
request with 0 topics so if you had no topics, you would have to ask for _all_ topics. Fixed
in 0.10.0.0, as I said.

> Clients retain metadata for non-subscribed topics
> -------------------------------------------------
>
>                 Key: KAFKA-3892
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3892
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients
>    Affects Versions: 0.9.0.1
>            Reporter: Noah Sloan
>
> After upgrading to 0.9.0.1 from 0.8.2 (and adopting the new consumer and producer classes,)
we noticed services with small heap crashing due to OutOfMemoryErrors. These services contained
many producers and consumers (~20 total) and were connected to brokers with >2000 topics
and over 10k partitions. Heap dumps revealed that each client had 3.3MB of Metadata retained
in their Cluster, with references to topics that were not being produced or subscribed to.
While the services were running with 128MB of heap prior to the upgrade, we to had increased
max heap to 200MB to accommodate all the extra data. 
> While this is not technically a memory leak, it does impose a significant overhead on
clients when connected to a large cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message