From: Oleksandr Shulgin
Sent: Wednesday, November 20, 2024 4:51 AM
To: users@kafka.apache.org
Subject: [EXTERNAL] Re: Spread primary and replica of a partition across
different zones in AWS
On Wed, Nov 20, 2024 at 9: 15 AM Soham Chakraborty
wrote: > > So my goal is to know whether th
From: Oleksandr Shulgin
Sent: Wednesday, November 20, 2024 3:51 AM
To: users@kafka.apache.org
Subject: [EXTERNAL] Re: Spread primary and replica of a partition across
different zones in AWS
On Wed, Nov 20, 2024 at 9: 15 AM Soham Chakraborty
wrote: > > So my goal is to know whether th
Alright. We were not initially using rack aware strategies. So primary and
replica were often spread in the same zone (same rack). We then added rack
awareness to the server.properties file and restarted the brokers. But of
course the partitions were not spread evenly. Now we will manually spread
t
On Wed, Nov 20, 2024 at 11:11 AM Soham Chakraborty
wrote:
> Fair enough. For one time task, we can probably use some manual work with
> sprinkling of automation thrown in. I will look into cruise control.
>
> Question: now that Kafka knows about "rack" future assignments should
> strictly be zone
Fair enough. For one time task, we can probably use some manual work with
sprinkling of automation thrown in. I will look into cruise control.
Question: now that Kafka knows about "rack" future assignments should
strictly be zone aware, is that a correct assessment? IOW, if a partition
is thrown o
On Wed, Nov 20, 2024 at 9:15 AM Soham Chakraborty
wrote:
>
> So my goal is to know whether there is any knob by which I can force the
> leader and replica to go to different AZs and is there any automated
> way/tool to handle this for existing partitions. In other words, I want the
> leader and
