After creating a topic, broker gets dropped from ISR

Hi again, 192.168.1.180 Zk: 192.168.1.180:2181 Kafka: 9092 Broker.id = 1 zookeeper.connect=192.168.1.180:2181 -- 192.168.1.190 Zk: 192.168.1.180:2181 Kafka: 9092 Broker.id = 2 zookeeper.connect=192.168.1.180:2181 -- I start both Kafka-server I create a topic using the following command

Broker don't get back in ISR when killed and restarted

Hi There, Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT Kafka version: kafka_2.8.0-0.8.1.1 192.168.1.180 zookeeper:2181 broker:9092(broker.id=1) zookeeper.connect=localhost:2181 192.168.1.190 broker:9092(broker.id=2) zookeeper.connect=192.168.1.180:2181 1) I start both kafka

Consumers don't get any data if broker leader is down

Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT Kafka version: kafka_2.8.0-0.8.1.1 I have the following architecture/configuration staging2.mtl.shopmedia.com (broker.id=1) zookeeper:9092 kafka:2181 staging3.mtl.shopmedia.com(broker.id=2) zookeeper:9092 kafka:2181 centos.mtl

Consumers don't get data when broker leader is down

ker leader, my consumers can't catch up ( I suspect this is because ISR is not up to date ) Any idea ? -- *Florent Valdelievre* (514) 756-0129 *florentvaldelie...@gmail.com * Find me on Linkedin <http://au.linkedin.com/pub/florent-valdelievre/63/975/9b7/>

Consumers don't get data when broker leader is down

Hi there, Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT Kafka version: kafka_2.8.0-0.8.1.1 I have the following architecture/configuration staging2.mtl.shopmedia.com (broker.id=1) zookeeper:9092 kafka:2181 staging3.mtl.shopmedia.com(broker.id=2) zookeeper:9092 kafka:2181 cent