[
https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043480#comment-16043480
]
Jun Rao commented on KAFKA-5402:
--------------------------------
Not sure if this is the same as KAFKA-3980. Currently, if a metric is not being
actively updated (after the client is gone), the metric is supposed to be
automatically removed after 1 hour.
Also, it seem that currently even if quota is not enabled, we still create the
quota metric with the client-id. Not sure how useful those metrics are w/o
enabling quota. Perhaps we should only create the metric if quota is enabled.
[~rsivaram], what do you think?
> JmxReporter Fetch metrics for kafka.server should not be created when client
> quotas are not enabled
> ---------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5402
> URL: https://issues.apache.org/jira/browse/KAFKA-5402
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.1.1
> Reporter: Koelli Mungee
> Attachments: Fetch.jpg, Metrics.jpg
>
>
> JMXReporter kafka.server Fetch metrics should not be created when client
> quotas are not enforced for client fetch requests. Currently, these metrics
> are created and this can cause OutOfMemoryException in the KafkaServer in
> cases where a large number of consumers are being created rapidly.
> Attaching screenshots from a heapdump showing the
> kafka.server:type=Fetch,client-id=consumer-358567 with different client.ids
> from a kafkaserver where client quotas were not enabled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
