[
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-v3.patch
One caveat in this approach is that if a fetcher is wedged for any reason, then
the reported lag is inaccurate since it depends on getting the high watermark
from fetch responses. i.e., to check on the health of a consumer you would need
to look at both the max lag and min fetch rate across all fetchers.
> 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,
> KAFKA-921-v3.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
