Open hgeraldino opened 3 hours ago
https://github.com/confluentinc/librdkafka/pull/4442 addressed an issue where offsets where not committed when leader epoch was the default (-1).
We've seen a different corner case, where offsets are not committed if the leader epoch is zero. This happens when enable.partition.eof is set to true and the fetcher reaches _PARTITION_EOF, as can be seen in the attached logs
enable.partition.eof
_PARTITION_EOF
Client configuration:
group.id: my-group auto.commit.interval.ms: 1000 enable.auto.commit: true auto.offset.reset: smallest
IMPORTANT: We will close issues where the checklist has not been completed.
Please provide the following information:
2.4.0
3.4.1
<REPLACE with e.g., message.timeout.ms=123, auto.reset.offset=earliest, ..>
Red Hat Enterprise Linux 8.4 (x64)
debug=..
export-filtered.txt
Description
https://github.com/confluentinc/librdkafka/pull/4442 addressed an issue where offsets where not committed when leader epoch was the default (-1).
We've seen a different corner case, where offsets are not committed if the leader epoch is zero. This happens when
enable.partition.eof
is set to true and the fetcher reaches_PARTITION_EOF
, as can be seen in the attached logsHow to reproduce
Client configuration:
Checklist
IMPORTANT: We will close issues where the checklist has not been completed.
Please provide the following information:
2.4.0
3.4.1
<REPLACE with e.g., message.timeout.ms=123, auto.reset.offset=earliest, ..>
Red Hat Enterprise Linux 8.4 (x64)
debug=..
as necessary) from librdkafka