[KAFKA-5402] JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.1.1
• Fix Version/s: 1.0.0
• Component/s: core
• Assignee: Rajini Sivaram
• Reporter: Koelli Mungee
• Created: 07/Jun/17 21:08
• Updated: 29/Jun/17 12:03
• Resolved: 29/Jun/17 12:02

Description

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.

Issue Links

• links to: GitHub Pull Request #3303