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
In Kafka, the offsets are stored for a limited period of time (24h by default), and if the consumer did not commit them during that period, they get wiped.
There is "periodic commit" logic in reactor-kafka, but it removes consumedOffsets during the commit:
In Kafka, the offsets are stored for a limited period of time (24h by default), and if the consumer did not commit them during that period, they get wiped.
There is "periodic commit" logic in reactor-kafka, but it removes consumedOffsets during the commit:
reactor-kafka/src/main/java/reactor/kafka/receiver/internals/CommittableBatch.java
Line 67 in 3bd1962
If partition did not receive any events for the past 24h, no commit will be performed and Kafka will delete the offset for that partition.
Reactor Kafka should support a "refresh" of already committed offsets to avoid that.
See a similar issue in Akka's reactive-kafka:
akka/alpakka-kafka#375
The text was updated successfully, but these errors were encountered: