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
It seems that it is using SmallRye kafka connector behind the scenes, and recommends the throtttled strategy to achieve highest throughput with reactive consumers, while still guaranteeing that offsets committed periodically aren't accidentally done for records which haven't completed processing.
Currently, the only way to get this working in Micronaut is to use reactive types, but then to manually acknowledge each consumer record, which reduces the throughput and adds load to the broker, OR to use @Blocking on the consumer.
The text was updated successfully, but these errors were encountered:
brianwyka
changed the title
Feature Request: More Robust Reactive / Async Support for Offset Commits
Feature Request: More Robust Reactive / Async Support for Periodic Offset Commits
Mar 8, 2021
I was reading over an article by Quarkus which discusses async consumers and when to commit offsets:
https://quarkus.io/blog/kafka-commit-strategies/
It seems that it is using
SmallRye
kafka connector behind the scenes, and recommends thethrotttled
strategy to achieve highest throughput with reactive consumers, while still guaranteeing that offsets committed periodically aren't accidentally done for records which haven't completed processing.Currently, the only way to get this working in Micronaut is to use reactive types, but then to manually acknowledge each consumer record, which reduces the throughput and adds load to the broker, OR to use
@Blocking
on the consumer.The text was updated successfully, but these errors were encountered: