kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Gustafson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4429) records-lag should be zero if FetchResponse is empty
Date Tue, 03 Jan 2017 22:11:58 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Gustafson resolved KAFKA-4429.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.2.0

Issue resolved by pull request 2155
[https://github.com/apache/kafka/pull/2155]

> records-lag should be zero if FetchResponse is empty
> ----------------------------------------------------
>
>                 Key: KAFKA-4429
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4429
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Dong Lin
>            Assignee: Dong Lin
>             Fix For: 0.10.2.0
>
>
> In Fetcher we record records-lag in terms of number of records for any partition. Currently
this metric value is updated only if number of parsed records is not empty. This means that
if consumer has already fully caught up and there is no new data into the topic, this metric's
value will be negative infinity and users can not rely on this metric to know if their consumer
has caught up.
> We can fix this problem by assuming the lag is zero is FetchResponse is empty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message