zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator-zipkin-reporter-java] adriancole commented on issue #143: Fixes socket reset problem in libthrift sender
Date Wed, 08 May 2019 13:34:16 GMT
adriancole commented on issue #143: Fixes socket reset problem in libthrift sender
URL: https://github.com/apache/incubator-zipkin-reporter-java/pull/143#issuecomment-490487520
 
 
   @jeqo I'm gonna turn in for the night soon. In case you have some time, there's an unrelated
fail here in the kafka sender. If you know a quick fix please raise in a different PR and
I will rebase.
   
   ```
   [2019-05-08T13:20:42.976Z] 13:20:37.414 [main] WARN  o.a.k.c.admin.AdminClientConfig -
The configuration 'key.serializer' was supplied but isn't a known config.
   
   [2019-05-08T13:20:42.976Z] [ERROR] Tests run: 9, Failures: 0, Errors: 1, Skipped: 0, Time
elapsed: 51.763 s <<< FAILURE! - in zipkin2.reporter.kafka11.KafkaSenderTest
   
   [2019-05-08T13:20:42.976Z] [ERROR] sendsSpansToCorrectTopic(zipkin2.reporter.kafka11.KafkaSenderTest)
 Time elapsed: 7.711 s  <<< ERROR!
   
   [2019-05-08T13:20:42.976Z] java.util.concurrent.ExecutionException: org.apache.kafka.clients.consumer.CommitFailedException:
Commit cannot be completed since the group has already rebalanced and assigned the partitions
to another member. This means that the time between subsequent calls to poll() was longer
than the configured max.poll.interval.ms, which typically implies that the poll loop is spending
too much time message processing. You can address this either by increasing max.poll.interval.ms
or by reducing the maximum size of batches returned in poll() with max.poll.records.
   
   [2019-05-08T13:20:42.976Z] 	at zipkin2.reporter.kafka11.KafkaSenderTest.readMessage(KafkaSenderTest.java:188)
   
   [2019-05-08T13:20:42.976Z] 	at zipkin2.reporter.kafka11.KafkaSenderTest.sendsSpansToCorrectTopic(KafkaSenderTest.java:102)
   
   [2019-05-08T13:20:42.976Z] Caused by: org.apache.kafka.clients.consumer.CommitFailedException:
Commit cannot be completed since the group has already rebalanced and assigned the partitions
to another member. This means that the time between subsequent calls to poll() was longer
than the configured max.poll.interval.ms, which typically implies that the poll loop is spending
too much time message processing. You can address this either by increasing max.poll.interval.ms
or by reducing the maximum size of batches returned in poll() with max.poll.records.
   
   [2019-05-08T13:20:42.976Z] 
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message