Re: Kafka rack-id and min in-sync replicas

I think you are right, The rack awareness is used to spread the partitions on creation, assignment -etc so get as many racks as your replication count. /svante 2017-08-20 13:33 GMT+02:00 Carl Samuelson : > Hi > > I asked this question on SO here: >

Kafka rack-id and min in-sync replicas

Hi I asked this question on SO here: https://stackoverflow.com/questions/45778455/kafka-rack-id-and-min-in-sync-replicas. Basically, I am trying to understand how rack-id helps in DR situations. Kafka has introduced rack-id to provide redundancy capabilities if a whole rack fails. There is a min

Kafka cluster startup synchronization and monitoring

I have the following configuration in Kafka cluster : 3 server where 3 brokers each are running (in all 9 brokers). Each server has 1 instance of Zookeeper running. When Kafka cluster is coming up, I don't want any producers and consumers to connect to any brokers until the cluster is fully

ZooKeeper issues with 3.4.9 0 Please Help

Hi I am trying to use the zookeeper 3.4.9 build (and jars) from apache zookeeper's site with Kafka 10.2.1. I want to run a 3 node zk cluster eventually, but to begin with I have only one node. I created my zoo.cfg as follows: tickTime=2000 dataDir=/var/lib/zookeeper/ clientPort=2181 initLimit=5