Details
-
Task
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
When auto-commit is enabled, the consumer (legacy and new) will continuously send commit requests with the current positions, even if no progress is made and positions remain unchanged. We could consider if this is really needed for some reason, or if we could improve it and just send auto-commit on the interval if positions have moved, avoiding sending repeatedly the same commit request.
Attachments
Issue Links
- is related to
-
KAFKA-16235 auto commit still causes delays due to retriable UNKNOWN_TOPIC_OR_PARTITION
- Open