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

Posted to dev@kafka.apache.org by "Grayson Chao (JIRA)" <ji...@apache.org> on 2015/03/09 18:32:38 UTC

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

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

Grayson Chao commented on KAFKA-1983:
-------------------------------------

Mind if I work on this? I'm brand new to the codebase and this seems as good a place to start as any.

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