The jmx is only available in the high level consumer. If you are using
SimpleConsumer, you have to calculate this yourself (hw from fetchresponse
- fetch offset).
Thanks,
Jun
On Fri, Oct 3, 2014 at 5:32 AM, Devang Shah wrote:
> Refering to the monitoring secton available on the kafka doc websi
The MaxLag mbean is only valid for an active consumer. So while the
consumer is actively running, it should be accurate.
On Fri, Oct 3, 2014 at 4:21 AM, Shah, Devang1 wrote:
> Hi,
>
> Referring to http://kafka.apache.org/documentation.html#java
>
>
> Number of messages the consumer lags behind t
Hi,
Referring to http://kafka.apache.org/documentation.html#java
Number of messages the consumer lags behind the producer by
"kafka.consumer":name="([-.\w]+)-MaxLag",type="ConsumerFetcherManager"
I could not find MBean kafka.consumer when I hooked up jconsole to kafka
server. I am using kaf
Refering to the monitoring secton available on the kafka doc website I am
unable to see kafka.consumer bean on the jconsole. Is this bean not exposed
via jconsole ?
"kafka.consumer":name="([-.\w]+)-MaxLag",type="ConsumerFetcherManager"
I am using kafka-0.8.1.1.
Also when I try to connect via a j
I tried hooking up jconsole to Kafka server but could not see the
"kafka.consumer" MBean.
I am using kafka_2.9.2-0.8.1.1
Am I going wrong anywhere ?
Thanks,
Devang
OK, thanks,
Do you agree then that the docs for auto topic creation configuration
parameter are misleading and should be changed?
Another issue is that when the topic auto creation is disabled, attempts to
publish a message on a non-existing topic using high-level api will throw a
generic FailedT