[
https://issues.apache.org/jira/browse/KAFKA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386040#comment-14386040
]
Sriharsha Chintalapani commented on KAFKA-1983:
-----------------------------------------------
[~gchao] Here are the steps
1) start a single node kafka server
2) create a topic "test"
3) ./bin/kafka-run-class.sh kafka.tools.TestEndToEndLatency localhost:9092
localhost:2181 test 100000 1000 1
(USAGE: java kafka.tools.TestEndToEndLatency$ broker_list zookeeper_connect
topic num_messages consumer_fetch_max_wait producer_acks)
4) hard kill the TestEndToEndLatency
5) restarting the number 3 step causes it report low latency.
> 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)
