Hey Shekar, Are you running with 0.8.0 when you run these tests? If so, there are some known issues where a Samza consumer can get stuck when brokers disappeared. All known issues have been resolved in the 0.9.0 release, but they exist in the 0.8.0 release.
Cheers, Chris On Mon, Mar 30, 2015 at 5:26 PM, Shekar Tippur <ctip...@gmail.com> wrote: > One more thing .. > > We have this configured as well. > > > systems.kafka.producer.metadata.broker.list=sprfargas102:6667,sprfargas103:6667 > > On Mon, Mar 30, 2015 at 5:08 PM, Shekar Tippur <ctip...@gmail.com> wrote: > > > Hello, > > > > I realise this is a Kafka question. Since there are quite a few Kafka > > experts here and the answer to this question can help Samza community as > > well, bringing this question here. > > > > We are testing Kafka redundancy (just 2 brokers for now). > > > > We have increased replication factor to 2 servers (Both kafka brokers) > > We have included auto.leader.rebalance.enable=true so that the leader > gets > > redundancy and bounced Kafka. > > We have moved the topic across both the servers. > > > > Below table shows the sequence of events. Can someone please explain why > > we see this behaviour in step 4? > > > > > > > > Broker 1 > > > > Broker 2 > > > > Kafka status > > > > Step 1 > > > > Up > > > > Up > > > > Running > > > > Step 2 > > > > Down > > > > Up > > > > Running > > > > Step 3 > > > > Up > > > > Up > > > > Running > > > > Step 4 > > > > Up > > > > Down > > > > Not running (Connection refused) > > >
