I guess once stream app are enabled exactly-once, producer idempotence get enabled by default and so do the retries. I guess producer retries are managed internally and not exposed through streamconfig.
https://kafka.apache.org/0110/documentation/#streamsconfigs -Sameer. On Thu, Sep 28, 2017 at 12:12 AM, Matthias J. Sax <matth...@confluent.io> wrote: > An OutOfOrderSequenceException should only occur if a idempotent > producer gets out of sync with the broker. If you set > `enable.idempotence = true` on your producer, you might want to set > `retries = Integer.MAX_VALUE`. > > -Matthias > > On 9/26/17 11:30 PM, Sameer Kumar wrote: > > Hi, > > > > I again received this exception while running my streams app. I am using > > Kafka 11.0.1. After restarting my app, this error got fixed. > > > > I guess this might be due to bad network. Any pointers. Any config > > wherein I can configure it for retries. > > > > Exception trace is attached. > > > > Regards, > > -Sameer. > >
