You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
confluent-kafka-go: 1.4.2
librdkafka: 17040127 1.4.2-dirty
broker: cp-kafka docker image, tried with 5.3.1 (Kafka 2.3.0) and 5.5.1 (Kafka 2.5.0)
OS: Linux 5.7.17-2-MANJARO
When sending consumer offsets as part of a transaction and retrieving the consumer offsets with .Committed immediately after committing the transaction the returned offsets are not the ones sent in the transaction. If there is a small delay between committing and retrieving, the offsets are correct.
@roignpar not sure that's your issue but: from what I remember the transaction adds some "markers" as message into the topic, and the .Committed() won't reflect the truth.
Try to use .Position() with the right TopicPartition{} instead :)
Description
confluent-kafka-go: 1.4.2
librdkafka: 17040127 1.4.2-dirty
broker: cp-kafka docker image, tried with
5.3.1 (Kafka 2.3.0)
and5.5.1 (Kafka 2.5.0)
OS: Linux 5.7.17-2-MANJARO
When sending consumer offsets as part of a transaction and retrieving the consumer offsets with
.Committed
immediately after committing the transaction the returned offsets are not the ones sent in the transaction. If there is a small delay between committing and retrieving, the offsets are correct.How to reproduce
Output:
Broker logs are quite verbose, seems to ignore LOG4J env config vars.
Checklist
Please provide the following information:
LibraryVersion()
):ConfigMap{...}
"debug": ".."
as necessary)The text was updated successfully, but these errors were encountered: