[
https://issues.apache.org/jira/browse/KAFKA-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Koshy updated KAFKA-921:
-----------------------------
Attachment: KAFKA-921-v2.patch
Yes - I think that would be better. Moved it to AbstractFetcherManager. So
depending on whether you are looking at replica fetchers or consumer fetchers,
the MaxLag mbean will show up in ReplicaFetcherManager or
ConsumerFetcherManager respectively.
> Expose max lag mbean for consumers and replica fetchers
> -------------------------------------------------------
>
> Key: KAFKA-921
> URL: https://issues.apache.org/jira/browse/KAFKA-921
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Joel Koshy
> Fix For: 0.8
>
> Attachments: KAFKA-921-v1.patch, KAFKA-921-v2.patch
>
>
> We have a ton of consumer mbeans with names that are derived from the
> consumer id, broker being fetched from, fetcher id, etc. This makes it
> difficult to do basic monitoring of consumer/replica fetcher lag - since the
> mbean to monitor can change. A more useful metric for monitoring purposes is
> the maximum lag across all fetchers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
