Re: How Producer handles Network Connectivity Issues

2015-05-29 Thread Bhavesh Mistry
Hi Kamal, In order to monitor each instance of producer, you will need to have alternative network monitoring channel (e.g Flume or Another Kafka Cluster for just monitoring a producers at large scale). Here is detail: 1) Add Custom Appender for Log4J and intercept all logs of Kafka Producer

Re: How Producer handles Network Connectivity Issues

2015-05-27 Thread Kamal C
Thanks for the response Ewen! On Tue, May 26, 2015 at 10:52 PM, Ewen Cheslack-Postava e...@confluent.io wrote: It's not being switched in this case because the broker hasn't failed. It can still connect to all the other brokers and zookeeper. The only failure is of the link between a client

Re: How Producer handles Network Connectivity Issues

2015-05-26 Thread Ewen Cheslack-Postava
It's not being switched in this case because the broker hasn't failed. It can still connect to all the other brokers and zookeeper. The only failure is of the link between a client and the broker. Another way to think of this is to extend the scenario with more producers. If I have 100 other

How Producer handles Network Connectivity Issues

2015-05-25 Thread Kamal C
Hi, I have a cluster of 3 Kafka brokers and a remote producer. Producer started to send messages to *SampleTopic*. Then I blocked the network connectivity between the Producer and the leader node for the topic *SampleTopic* but network connectivity is healthy between the cluster and producer