kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guozhang Wang <wangg...@gmail.com>
Subject Re: What's the behavior when Kafka is deleting messages and consumers are still reading
Date Tue, 24 Jun 2014 23:23:52 GMT
I think we can probably update the documentation page for this update:

https://kafka.apache.org/documentation.html#compaction


On Tue, Jun 24, 2014 at 3:54 PM, Lian, Li <llian@ebay.com> wrote:

> GuoZhang,
>
> Thanks for explaining. I thought there might be such kind of lock
> mechanism but cannot confirm it in any documentation on Kafka website.
>
> It will be better if this could be written down in some Wiki or FAQ.
>
>
> Best regards,
> Lex Lian
>
> Email: llian@ebay.com
>
>
>
>
>
> On 6/24/14, 11:17 PM, "Guozhang Wang" <wangguoz@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 <llian@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: llian@ebay.com
> >>
> >>
> >
> >
> >--
> >-- Guozhang
>
>


-- 
-- Guozhang

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message