Open ennru opened 4 years ago
My first idea here would have been to enable idempotence on the producer that produces the grouped messages to topic-2
, but if dupes were generated by this producer then I would expect distinct offsets for them in the topic-2
.
Based on the results of the last failure it looks like the second consumer is reading the same messages from topic-2
twice. The test expects the results to be of size 2, but 4 are returned with duplicate offsets in the ConsumerRecord
. Formatted:
Vector(
ConsumerRecord(topic = topic-2-96, partition = 0, leaderEpoch = 0, offset = 0, CreateTime = 1594127538548, serialized key size = 3, serialized value size = 9, headers = RecordHeaders(headers = [], isReadOnly = false), key = key, value = 1,2,3,4,5),
ConsumerRecord(topic = topic-2-96, partition = 0, leaderEpoch = 0, offset = 1, CreateTime = 1594127538548, serialized key size = 3, serialized value size = 10, headers = RecordHeaders(headers = [], isReadOnly = false), key = key, value = 6,7,8,9,10),
ConsumerRecord(topic = topic-2-96, partition = 0, leaderEpoch = 0, offset = 0, CreateTime = 1594127538548, serialized key size = 3, serialized value size = 9, headers = RecordHeaders(headers = [], isReadOnly = false), key = key, value = 1,2,3,4,5),
ConsumerRecord(topic = topic-2-96, partition = 0, leaderEpoch = 0, offset = 1, CreateTime = 1594127538548, serialized key size = 3, serialized value size = 10, headers = RecordHeaders(headers = [], isReadOnly = false), key = key, value = 6,7,8,9,10)
)
In the scheduled build https://travis-ci.org/github/akka/alpakka-kafka/jobs/725973526
First seen in #1069
https://travis-ci.org/akka/alpakka-kafka/jobs/657205159#L490