kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajini Sivaram (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled
Date Thu, 29 Jun 2017 12:03:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajini Sivaram resolved KAFKA-5402.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.1.0

Issue resolved by pull request 3303
[https://github.com/apache/kafka/pull/3303]

> 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
>             Fix For: 0.11.1.0
>
>         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)

Mime
View raw message