You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When commits are not immediate and/or some events can have a relatively high processing time and topics substain a low traffic, it can lead to lag being reported even if events were processed and committed.
Describe the bug
When commits are not immediate and/or some events can have a relatively high processing time and topics substain a low traffic, it can lead to lag being reported even if events were processed and committed.
Kafka Version
3.6.x
To Reproduce
This test reprocuces the behavior:
https://github.com/nachogiljaldo/kafka-go/blob/do_not_commit_offset_of_not_owned_partitions/reader_test.go#L1184
The situation is:
Expected Behavior
There are 2 things I would expect:
Observed Behavior
We do not get the missing message which leads to a fake lag when the traffic has little traffic.
The text was updated successfully, but these errors were encountered: