You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Matthias (Jira)" <ji...@apache.org> on 2020/12/18 11:17:00 UTC

[jira] [Closed] (FLINK-16714) Kafka committedOffsets value <0

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

Matthias closed FLINK-16714.
----------------------------
    Resolution: Won't Fix

Thanks [~ambition119] for bringing it up. As [~chesnay] pointed out, there's no real solution for the problem. Hence, I'm closing this ticket as part of the Engine team's backlog grooming.

> Kafka committedOffsets value <0
> -------------------------------
>
>                 Key: FLINK-16714
>                 URL: https://issues.apache.org/jira/browse/FLINK-16714
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>    Affects Versions: 1.6.3
>            Reporter: pingle wang
>            Priority: Major
>         Attachments: image-2020-03-23-15-36-16-487.png, image-2020-03-23-15-36-27-910.png
>
>
> dear all:
>        use rest api get kafka offsets sometimes produces errors value like < 0, so use this value monitoring Kafka's lag size will produce false positives. This should be the problem of flink metrics collection?
> thanks!
> !image-2020-03-23-15-36-27-910.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)