[
https://issues.apache.org/jira/browse/KAFKA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18110003#comment-18110003
]
Rishabh Saraswat edited comment on KAFKA-1983 at 8/31/26 6:51 PM:
------------------------------------------------------------------
[~junrao] I would like to work on this, can you please assign me this ticket.
was (Author: JIRAUSER311726):
[~junrao][~gchao] I would like to work on this, can you please assign me this
ticket.
> TestEndToEndLatency can be unreliable after hard kill
> -----------------------------------------------------
>
> Key: KAFKA-1983
> URL: https://issues.apache.org/jira/browse/KAFKA-1983
> Project: Kafka
> Issue Type: Improvement
> Reporter: Jun Rao
> Assignee: Rishabh Saraswat
> Priority: Major
> Labels: newbie
>
> 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)
