[
https://issues.apache.org/jira/browse/KAFKA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957018#comment-17957018
]
vinupreethi93 edited comment on KAFKA-1983 at 6/9/25 3:23 PM:
--------------------------------------------------------------
Hi, [~junrao]
How to reproduce this issue, i also couldnt see significant change
[https://github.com/apache/kafka/pull/19934] is this the change you are
expecting. is there any way we can connect on this.
was (Author: JIRAUSER309961):
Hi, [~junrao]
How to reproduce this issue, i also couldnt see significant change
> 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
> 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)
