Okay. Thanks for your help, I'll do some tests.
On Fri, Feb 21, 2020, at 23:40, Brian Sang wrote:
> I think so? We've always set both leader and follower, like the example on
> the page you linked earlier. But I don't see why just setting follower
> wouldn't work either.
>
> On Fri, Feb 21, 2020
I think so? We've always set both leader and follower, like the example on
the page you linked earlier. But I don't see why just setting follower
wouldn't work either.
On Fri, Feb 21, 2020 at 2:08 PM Vincent Rischmann
wrote:
> yeah that's not a bad idea.
>
> So to recap, it's enough to set follo
yeah that's not a bad idea.
So to recap, it's enough to set follower.replication.throttled.replicas for
every partition assigned to that broker ? I'm assuming that during bootstrap
the broker is a follower for everything.
On Fri, Feb 21, 2020, at 22:09, Brian Sang wrote:
> You can get the list
You can get the list of partitions that was on the broker that you
replaced. That way you don't need to apply throttle to every topic
partition in the cluster.
On Fri, Feb 21, 2020 at 4:48 AM Vincent Rischmann
wrote:
> Hi Brian,
>
> thanks for the recommendation. I do in fact plan to use autothr
Hi Brian,
thanks for the recommendation. I do in fact plan to use autothrottle (although
I need to make it work with our prometheus metrics first).
However if I understand correctly, I would need to apply a throttle to
essentially every partition of every topic, since in the use case I describe
Hey Vincent, I think you need to set both the configs for the brokers and
the individual partitions you are moving themselves.
For an automated system that can make this easier, check out
https://github.com/DataDog/kafka-kit/tree/master/cmd/autothrottle, though
it requires DataDog, you can use a s
