The behavior on the consumer in this case is governed by the value of the "auto.offset.reset" config. Depending on this config, it will reset it's offset to either the earliest or the latest in the log.
Thanks, Neha On Tue, Jun 24, 2014 at 8:17 AM, Guozhang Wang <wangg...@gmail.com> wrote: > Hi Li, > > The log operations are protected by a lock, so if there is a concurrent > read on this partition it will not be deleted. But then when it is deleted > the next fetch/read will result in a OffsetOutOfRange exception and the > consumer needs to restart from a offset reset value. > > Guozhang > > > On Tue, Jun 24, 2014 at 5:20 AM, Lian, Li <ll...@ebay.com> wrote: > > > When Kafka broker is trying to delete message according to the log > > retention setting, either triggered by log age or topic partition size, > if > > the same time there are still consumers reading the topic, what will > happen? > > > > Best regards, > > Lex Lian > > > > Email: ll...@ebay.com > > > > > > > -- > -- Guozhang >
