Hi, I'm having the same setup as Dimitry, I've experienced exactly the same issue already 2 times this last month. (the only difference with Dimitry's setup is that I have librdkafka 0.9.5 clients.
It's like if the __consumer_offsets partitions were not synced but still reported as synced (and so the syncing would never be restarted/continued). I've never experienced that on Kafka 0.9.x or 0.10.x clusters. the 0.11.0.0 cluster when it happened got upgraded to 0.11.0.1 in hope it fixes this. On Fri, Oct 6, 2017 at 5:35 PM, Manikumar <manikumar.re...@gmail.com> wrote: > normally, log.retention.hours (168hrs) should be higher than > offsets.retention.minutes (336 hrs)? > > > On Fri, Oct 6, 2017 at 8:58 PM, Dmitriy Vsekhvalnov < > dvsekhval...@gmail.com> > wrote: > > > Hi Ted, > > > > Broker: v0.11.0.0 > > > > Consumer: > > kafka-clients v0.11.0.0 > > auto.offset.reset = earliest > > > > > > > > On Fri, Oct 6, 2017 at 6:24 PM, Ted Yu <yuzhih...@gmail.com> wrote: > > > > > What's the value for auto.offset.reset ? > > > > > > Which release are you using ? > > > > > > Cheers > > > > > > On Fri, Oct 6, 2017 at 7:52 AM, Dmitriy Vsekhvalnov < > > > dvsekhval...@gmail.com> > > > wrote: > > > > > > > Hi all, > > > > > > > > we several time faced situation where consumer-group started to > > > re-consume > > > > old events from beginning. Here is scenario: > > > > > > > > 1. x3 broker kafka cluster on top of x3 node zookeeper > > > > 2. RF=3 for all topics > > > > 3. log.retention.hours=168 and offsets.retention.minutes=20160 > > > > 4. running sustainable load (pushing events) > > > > 5. doing disaster testing by randomly shutting down 1 of 3 broker > nodes > > > > (then provision new broker back) > > > > > > > > Several times after bouncing broker we faced situation where consumer > > > group > > > > started to re-consume old events. > > > > > > > > consumer group: > > > > > > > > 1. enable.auto.commit = false > > > > 2. tried graceful group shutdown, kill -9 and terminating AWS nodes > > > > 3. never experienced re-consumption for given cases. > > > > > > > > What can cause that old events re-consumption? Is it related to > > bouncing > > > > one of brokers? What to search in a logs? Any broker settings to try? > > > > > > > > Thanks in advance. > > > > > > > > > > -- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
