kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [kafka] branch trunk updated: KAFKA-6724; ConsumerPerformance should not always reset to earliest offsets (#4787)
Date Wed, 28 Mar 2018 17:33:28 GMT
This is an automated email from the ASF dual-hosted git repository.

jgus pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/trunk by this push:
     new dd70117  KAFKA-6724; ConsumerPerformance should not always reset to earliest offsets
(#4787)
dd70117 is described below

commit dd7011783f7e013a0a40a0d4d0e38ac2612b36e1
Author: Alex D <rootex-@users.noreply.github.com>
AuthorDate: Wed Mar 28 20:33:23 2018 +0300

    KAFKA-6724; ConsumerPerformance should not always reset to earliest offsets (#4787)
    
    Remove the explicit `seekToBeginning` on startup and instead rely on the consumer's auto
offset reset strategy to set the initial position.
---
 core/src/main/scala/kafka/tools/ConsumerPerformance.scala | 2 --
 1 file changed, 2 deletions(-)

diff --git a/core/src/main/scala/kafka/tools/ConsumerPerformance.scala b/core/src/main/scala/kafka/tools/ConsumerPerformance.scala
index a3e60e6..7e0dbcb 100644
--- a/core/src/main/scala/kafka/tools/ConsumerPerformance.scala
+++ b/core/src/main/scala/kafka/tools/ConsumerPerformance.scala
@@ -157,8 +157,6 @@ object ConsumerPerformance extends LazyLogging {
       def onPartitionsRevoked(partitions: util.Collection[TopicPartition]) {
         joinStart = System.currentTimeMillis
       }})
-    consumer.poll(0)
-    consumer.seekToBeginning(Collections.emptyList())
 
     // Now start the benchmark
     val startMs = System.currentTimeMillis

-- 
To stop receiving notification emails like this one, please contact
jgus@apache.org.

Mime
View raw message