[
https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046540#comment-16046540
]
ASF GitHub Bot commented on KAFKA-5402:
---------------------------------------
GitHub user rajinisivaram opened a pull request:
https://github.com/apache/kafka/pull/3303
KAFKA-5402: Avoid creating quota related metrics if quotas not enabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rajinisivaram/kafka KAFKA-5402
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3303.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3303
----
commit f69011760d67a4b85d5049014e5929fbdc661858
Author: Rajini Sivaram <[email protected]>
Date: 2017-06-12T12:12:14Z
KAFKA-5402: Avoid creating quota related metrics if quotas not enabled
----
> 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
> Assignee: Rajini Sivaram
> 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.4.14#64029)
