RE: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-18 Thread Chris Peart
That's great, thanks for the detailed explanation Andrew. Chris -Original Message- From: Andrew Grant Sent: 18 December 2022 14:55 To: users@kafka.apache.org Subject: Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1 Hey Chris, Alex is right t

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-18 Thread Andrew Grant
y? > > Many Thanks, > Chris > > -Original Message- > From: Alex Craig > Sent: 17 December 2022 13:27 > To: users@kafka.apache.org > Subject: Re: __consumer_offsets & __transaction_state topics have > ReplicationFactor: 1 > > Andrew - your e

RE: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-18 Thread Chris Peart
er maintenance and resiliency? Many Thanks, Chris -Original Message- From: Alex Craig Sent: 17 December 2022 13:27 To: users@kafka.apache.org Subject: Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1 Andrew - your example would give him a replication f

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-17 Thread Alex Craig
Andrew - your example would give him a replication factor of 2 though, and it sounds like he wants 3 unless I missed something. So add an additional broker id to each of the replicas arrays in your example and you'd have an RF of 3. -alex On Sat, Dec 17, 2022 at 7:12 AM Andrew Grant wrote: > H

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-17 Thread Andrew Grant
Here's an example with four partitions which should be pretty easily extended to include up to partition 49: { "version": 1, "partitions": [ { "topic": "__consumer_offsets", "partition": 0, "replicas": [ 0, 1 ] }, { "topic": "__consumer_offsets", "parti

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-16 Thread Chris Peart
Hi Andrew, Would you be able to provide an example of the json with all the partitions in please, I tried this on our dev cluster but it didn’t work. Many Thanks, Chris > On 16 Dec 2022, at 9:03 pm, Andrew Grant wrote: > > Hey Chris, > > You'd need to do the same for all partitions. I just

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-16 Thread Andrew Grant
Hey Chris, You'd need to do the same for all partitions. I just showed partition 49 as an example - I picked 49 because when I ran a describe it showed up at the bottom of my terminal :) You could do all the partitions in the same reassignment. In that JSON I just put partition 49 but you could ad

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-16 Thread Chris Peart
Hi Andrew, Thanks for the speedy reply, so do I just need to do this for partition 49? What about partitions 0-48, will these be covered by reassigning partition 49. Do I need to do this for the __transaction_state topics too? Many thanks, Chris > On 16 Dec 2022, at 4:17 pm, Andrew Grant wro

Re: __consumer_offsets & __transaction_state topics have ReplicationFactor: 1

2022-12-16 Thread Andrew Grant
Hey Chris, I think you should be able to use the reassignment tool to add replicas. You should be able to do something similar to migrate the partitions away from the old brokers and onto the new ones and also increase the replication factor at the same time. I tested just increasing the replicatio