kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Bolshakov <bolshakov.de...@gmail.com>
Subject Re: How would Kafka behave in this scenario
Date Tue, 26 Sep 2017 12:34:03 GMT
By default kafkf does not allow dirty reads for clients, so while
`min.insync.replicas`
is not achieved consumers don't see new messages.

On 26 September 2017 at 11:09, Sameer Kumar <sam.kum.work@gmail.com> wrote:

> Thanks Stevo for pointing me out to correct link.
> In this case, how would exactly once feature of streams would behave since
> they configure producers with acks=all. I think they would fail and would
> need to be resumed once the broker comes back.
>
> -Sameer.
>
> On Tue, Sep 26, 2017 at 1:09 PM, Stevo Slavić <sslavic@gmail.com> wrote:
>
> > Hello Sameer,
> >
> > Behavior depends on min.insync.replicas configured for the topic.
> > Find more info in the documentation
> > https://kafka.apache.org/documentation/#topicconfigs
> >
> > Kind regards,
> > Stevo Slavic.
> >
> > On Tue, Sep 26, 2017 at 9:01 AM, Sameer Kumar <sam.kum.work@gmail.com>
> > wrote:
> >
> > > In case one of the brokers fail,  the broker would get removed from the
> > > respective ISR list of those partitions.
> > > In case producer has acks=all, how would it behave? would the producers
> > be
> > > throttled and wait till the broker get backed up.
> > >
> > > -Sameer.
> > >
> >
>



-- 
//with Best Regards
--Denis Bolshakov
e-mail: bolshakov.denis@gmail.com

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