[
https://issues.apache.org/jira/browse/KAFKA-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967925#comment-14967925
]
ASF GitHub Bot commented on KAFKA-2678:
---------------------------------------
GitHub user lindong28 opened a pull request:
https://github.com/apache/kafka/pull/346
KAFKA-2678; partition level lag metrics can be negative
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lindong28/kafka KAFKA-2678
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/346.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #346
----
commit 966d3aed1a796ddafd202f9ab467a06d7b804d2b
Author: Dong Lin <lindon...@gmail.com>
Date: 2015-10-21T21:12:21Z
KAFKA-2678; partition level lag metrics can be negative
----
> partition level lag metrics can be negative
> -------------------------------------------
>
> Key: KAFKA-2678
> URL: https://issues.apache.org/jira/browse/KAFKA-2678
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.2.1
> Reporter: Jun Rao
> Assignee: Dong Lin
>
> Currently, the per partition level lag metric can be negative since the last
> committed offset can be smaller than the follower's offset. This is a bit
> confusing to end users. We probably should lower bound it by 0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
