[
https://issues.apache.org/jira/browse/KAFKA-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15649233#comment-15649233
]
Guozhang Wang commented on KAFKA-4381:
--------------------------------------
To me, KIP is designed to solicit broader feedbacks from the community as well
as enforce proposers to think carefully about pros / cons of different
approaches as well as compatibility stories for certain changes, so changes
like this sounds like overkill for KIP. But when talking to other committers a
while ago I realized people have different opinions about this, so I'm OK to
just play the restrict rule on book for such things as well, unless over time
people it is hindering development pace and we can re-visit.
> 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
> 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
(v6.3.4#6332)
