本文介绍了卡夫卡消费者-JMX属性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在端口8081的kafka代理上启用了JMX.当我在jConsole中查看MBean属性时,我仅对kafka.consumer-

I enabled JMX on the kafka brokers on port 8081. When I view the MBean properties in jConsole, I only see the following for kafka.consumer-

kafka.consumer:type=FetchRequestAndResponseMetrics,name=FetchRequestRateAndTimeMs,clientId=ReplicaFetcherThread-2-413

kafka.consumer:type=FetchRequestAndResponseMetrics,name=FetchResponseSize,clientId=ReplicaFetcherThread-0-413

但在卡夫卡下的此处中没有发现其他任何一个消费者指标由JMX发出.

But none of the other ones that are identified in here under Kafka Consumer Metrics are emitted by JMX.

Kafka版本#0.8.2.1

Kafka Version # 0.8.2.1

我特别感兴趣-kafka.consumer:type=ConsumerFetcherManager,name=MaxLag,clientId=([-.\w]+)

有什么想法吗?

推荐答案

您正在监听的JMX PORT是代理端口.但是kafka.consumer:的Mbean是使用者jvm指标.因此,如果您有另一个使用主题的JVM,则可以看到kafka.consumer Mbeans.

The JMX PORT you are listening is the broker port. But the Mbean of kafka.consumer: is the consumer jvm metrics. So if you have another JVM that is consume a topic, you can see kafka.consumer Mbeans.

这篇关于卡夫卡消费者-JMX属性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-05 00:50