On Thu, Feb 18, 2016 at 8:03 PM, Jason Gustafson <ja...@confluent.io> wrote: > The consumer is single-threaded, so we only trigger commits in the call to > poll(). As long as you consume all the records returned from each poll > call, the committed offset will never get ahead of the consumed offset, and > you'll have at-lest-once delivery. Note that the implication is that " > auto.commit.interval.ms" is not strictly followed unless each iteration of > the loop takes less time than the configured commit interval.
Ah, that makes sense. Thank you! On Thu, Feb 18, 2016 at 8:30 PM, Jay Kreps <j...@confluent.io> wrote: > Yeah I didn't mean to imply that we committed after each poll, but rather > that when it was time to commit, this would happen on the next poll call > and hence only commit processed messages. Ah, cool, got it. Thank you!
