replica.fetch.max.bytes=1000default.replication.factor=2delete.topic.enable=trueunclean.leader.election.enable=falsecompression.type=snappy*
Any ideas?
Thanks in advance!
Seva Feldman
nodes
have 2.3 version and old one 2.2 version or we need to upgrade old one to
2.3 version to align interbroker.protocol.version before moving partitions.
BR
--
Seva Feldman
VP R&D Mobile Delivery
[image: ironSource] <http://www.ironsrc.com/>
email sev...@ironsrc.com
mobile +97
wouldn't
> have
> > > changed much. As far as our observation goes, it happens usually after
> a
> > > broker restart.
> > >
> > > Has anyone else come across this behavior?
> > >
> > > Thanks!
> > >
> >
> >
> > --
> > *Suman*
> > *OlaCabs*
> >
>
--
Seva Feldman
VP R&D Mobile Delivery
[image: ironSource] <http://www.ironsrc.com/>
email sev...@ironsrc.com
mobile +972544346089
ironSource HQ - 121 Derech Menachem Begin st. Tel Aviv
> >
> > During those spikes, do you observe any background operations going on?
> > Check server logs, controller logs.
> >
> > On Tue, Apr 7, 2020 at 12:49 PM Seva Feldman wrote:
> >
> > > ST1 EBS fit only for sequential rights and reads. Once you have ma
compressed
> segment.bytes 104857600
> max.message.bytes 5000
> min.compaction.lag.ms 4320
> message.timestamp.type LogAppendTime
> min.cleanable.dirty.ratio 0.1
>
> Consumer settings:
> max.partition.fetch.bytes=8048576
> fetch.max.byte