Hi Mehrtens,
That is expected with the current implementation of offset translation. It
makes a tradeoff that translation further from the end of the topic is less
accurate, and it won't "converge" to a perfect translation.
The only "perfect" translation that is offered is when the consumer group
HI - Apologies for the delay, it took me a while to find time to learn how to
build from source and incorporate that into my test environment. I've built off
of the 3.7.1-rc2 tag which includes the KAFKA-15905 fix. Unfortunately, this
did not fix the issue.
With 3.7.1-rc2, offset replication st
+1 (non-binding). I used the staged binaries (based on Scala 2.13) and
Maven artifacts to run my tests. All seems to work fine.
Thanks & Regards
Jakub
On Wed, Jun 19, 2024 at 10:55 AM Igor Soarez wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for
Hi all,
I have an issue that spans Kafka and K8s... Do you think a Kafka bug is
appropriate? Is there an alternative configuration to prevent this from
happening again? Would it be any different with KRaft?
Here's what happened:
* A big disruption occurs on a node running the kafka-2 broker. Lo
