Auto.offset.reset only comes into place when 1. the consumer fetches message from offset out of range - available offsets on broker side 2. The consumer group has no offset committed.
So in your case, I guess high level consumer has already committed its offset before and that offset is not out of range. When you start consume later with the same consumer group id, it will resume from the last committed offset. If you start a new consumer with a new consumer group and set auto.offset.reset to largest, you should see only new messages. Jiangjie (Becket) Qin On 5/28/15, 9:31 AM, "Panda, Samaresh" <samaresh.pa...@washpost.com> wrote: >I'm following this page >https://cwiki.apache.org/confluence/display/KAFKA/Consumer+Group+Example >and am able to consume messages using four threads. The threads keep >receiving messages, which is good. However, I just want to receive only >NEW messages and not the old ones. > >Since the default for auto.offset.reset is 'largest' I expected to >receive only new ones, but the messages keep coming including some really >old ones. > >Any other configuration or property change that lets me accomplish this? > >Thanks > > >
