[
https://issues.apache.org/jira/browse/KAFKA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371981#comment-14371981
]
Grayson Chao commented on KAFKA-1983:
-------------------------------------
I'm having some trouble reproducing this issue. Hard killing the process during
the test does not seem to cause a significant change in any of the latency
readings. Is there a more detailed set of repro steps somewhere I could use to
test my fix?
> 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: Grayson Chao
> 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
(v6.3.4#6332)
