[jira] [Commented] (KAFKA-1983) TestEndToEndLatency can be unreliable after hard kill

["Jun Rao (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334096#comment-14334096 ] 

Jun Rao commented on KAFKA-1983:
--------------------------------

An easy solution is probably to avoid committing offset at all. This way, the consumer will always resume consumption from the tail of the log on restart.

> 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
>              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)