[
https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044100#comment-16044100
]
Rajini Sivaram commented on KAFKA-5402:
---------------------------------------
[~junrao] Yes, agree that these metrics are only useful for quotas. We can
disable them when no quotas are configured. If anyone is interested in these
metrics without any throttling, it should be easy to set a very large (e.g.
Long.MAX_VALUE-1) default client-id quota (or default user quota to monitor at
user level).
> 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)
