[
https://issues.apache.org/jira/browse/KAFKA-9794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17077835#comment-17077835
]
Jordan Moore commented on KAFKA-9794:
-------------------------------------
Why use a separate Github with configs when Prometheus already maintains Kafka
examples?
[https://github.com/prometheus/jmx_exporter/tree/master/example_configs]
Additionally, I suspect this bug is actually in the JMX Exporter and due to the
fact it is actively trying to connect and process JMX metrics
> JMX metrics produce higher memory and CPU consumption in Kafka docker
> ---------------------------------------------------------------------
>
> Key: KAFKA-9794
> URL: https://issues.apache.org/jira/browse/KAFKA-9794
> Project: Kafka
> Issue Type: Bug
> Components: metrics
> Affects Versions: 2.2.0
> Environment: kafka version: kafka_2.12-2.2.0.tgz using docker
> Reporter: Hariprasad
> Priority: Major
> Labels: performance
>
> We have implemented the Kafka metrics using this github:
> [https://github.com/oded-dd/prometheus-jmx-kafka]
> we have enabled the metrics using KAFKA_OPTS. export
> KAFKA_OPTS='-javaagent:/etc/kafka/jmx_prometheus_javaagent-0.3.1.jar=9097:/etc/kafka/kafka-jmx-metrics.yaml'
> After starting the Kafka with this, we have seen high usage in CPU and memory
> shoot up in the docker
> CPU cycles goes some times as up as 300% , we are running with 4 cpu's
> Kindly suggest some solution how to fix this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
