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

Posted to jira@kafka.apache.org by "Rishabh Saraswat (Jira)" <ji...@apache.org> on 2026/09/11 08:25:00 UTC

[jira] [Closed] (KAFKA-1983) Remove redundant offset commits from EndToEndLatency

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

Rishabh Saraswat closed KAFKA-1983.
-----------------------------------

https://github.com/apache/kafka/commit/8f7674d3825b68b2dd8408080b79e5b83de54774

> Remove redundant offset commits from EndToEndLatency
> ----------------------------------------------------
>
>                 Key: KAFKA-1983
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1983
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 4.3.1
>            Reporter: Jun Rao
>            Assignee: Rishabh Saraswat
>            Priority: Major
>              Labels: newbie
>             Fix For: 4.3.2, 4.5.0
>
>
> If you hard kill TestEndToEndLatency, the committed offset remains the last checkpointed one. However, more messages are now appended after the last checkpointed offset. When restarting TestEndToEndLatency, the consumer resumes from the last checkpointed offset and will report really low latency since it doesn't need to wait for a new message to be produced to read the next message.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)