You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Dong Lin (JIRA)" <ji...@apache.org> on 2018/06/08 23:51:00 UTC
[jira] [Commented] (KAFKA-4381) Add per partition lag metric to
KafkaConsumer.
[ https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506710#comment-16506710 ]
Dong Lin commented on KAFKA-4381:
---------------------------------
The metric added in this patch includes topic partition in the metric name instead of tags. This introduces mbean whose number of attributes is proportional to the number of topic partition of the consumer. This can significantly reduces the MM startup time (see https://github.com/apache/kafka/pull/5011) because consumer needs to create O(n^2) number of objects for metrics during initialization. In the future we need to include topic partition in the tags of the metrics.
> Add per partition lag metric to KafkaConsumer.
> ----------------------------------------------
>
> Key: KAFKA-4381
> URL: https://issues.apache.org/jira/browse/KAFKA-4381
> Project: Kafka
> Issue Type: Task
> Components: clients, consumer
> Affects Versions: 0.10.1.0
> Reporter: Jiangjie Qin
> Assignee: Jiangjie Qin
> Priority: Major
> Labels: kip
> Fix For: 0.10.2.0
>
>
> Currently KafkaConsumer only has a metric of max lag across all the partitions. It would be useful to know per partition lag as well.
> I remember there was a ticket created before but did not find it. So I am creating this ticket.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)