Hi Bill, > When you say "even if the application has not had data for a long time" do you have a rough idea of how long?
Minutes, hours > What is the value of your "auto.offset.reset" configuration? I don't specify it explicitly, but the ConsumerConfig logs indicate "auto.offset.reset = earliest" for all consumers the application creates. Thank you, Dmitry On Thu, Jul 20, 2017 at 8:07 PM, Bill Bejeck <b...@confluent.io> wrote: > Hi Dmitry, > > When you say "even if the application has not had data for a long time" do > you have a rough idea of how long? What is the value of your > "auto.offset.reset" configuration? > > Thanks, > Bill > > On Thu, Jul 20, 2017 at 6:03 PM, Dmitry Minkovsky <dminkov...@gmail.com> > wrote: > > > My Streams application is configured to commit offsets every 250ms: > > > > Properties streamsConfig = new Properties(); > > streamsConfig.put(StreamsConfig.COMMIT_INTERVAL_MS_CONFIG, 250); > > > > > > However, every time I restart my application, records that have already > > been processed are re-processed, even if the application has not had data > > for a long time. > > > > My guess is that offsets are committed only when all tasks in the > topology > > have received input. Is this what's happening? > > > > > > > > Thank you, > > Dmitry > > >
