You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Evelyn Bayes (Jira)" <ji...@apache.org> on 2020/03/11 02:26:00 UTC

[jira] [Commented] (KAFKA-9680) Negative consumer lag

    [ https://issues.apache.org/jira/browse/KAFKA-9680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056598#comment-17056598 ] 

Evelyn Bayes commented on KAFKA-9680:
-------------------------------------

Hi [~blcksrx],

I expect this is due to edge case behaviour where you've deleted a topic and recreated it.
This would result in a situation where the stored offsets and the data are misaligned.

In the case of the HDFS connector it handled offsets via the data stored in hdfs.

Could you check if this is the case? Or could you provide a method for reproducing?

Otherwise, could you provide much more extensive logs, such as:
 * Kafka broker logs from all brokers;
 * Kafka connect worker logs from all workers; and
 * HDFS logs (ideally audit logs).

> Negative consumer lag
> ---------------------
>
>                 Key: KAFKA-9680
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9680
>             Project: Kafka
>          Issue Type: Bug
>          Components: consumer
>    Affects Versions: 2.3.1
>            Reporter: Sayed Mohammad Hossein Torabi
>            Assignee: Evelyn Bayes
>            Priority: Major
>
> I'm using Kafka 2.3.1 and got negative consumer lag on it. Here is the result of my consumergroup
> {code:java}
> //   1          18985           8576            -10409          connector-consumer-hdfs-sink-1-20e86f06-cf92-4b68-a67a-32e1876118f7 /172.16.2.220   connector-consumer-hdfs-sink-1
> {code}



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