Hi all,
We are using kafka - 0.8 in our production setup. We have 2 kafka servers
and 2 zookeepers. There seem to be some sort of network problem in our DC. As a
result of this, connection refused exception in replica which was thrown , is
shown here. Our producer didnt throw any exceptio
"TCP_TOO_MANY_ESTAB_CONNS"
warning message frequently. Why is this warning comes so frequently ?? Are we
are missing something ???
PS : Our monitoring tool's threshold is 600 connections
thanks in advance
Ranjith Venkatesan
Hi,We are about to use kafka-0.8 in our production. We have our config to delete messages less than a day i.e 24 hrs. We have our simple consumer which will have its offset in memory and will handle if offsetoutofrange exception occurs.Suppose if old log messages are getting deleted what will happe
configuration?
PS: I have attached the test code used for testing SimpleConsumer
Thanks in advance
Ranjith Venkatesan
package kafka.examples;
import java.util.logging.Level;
import java.util.logging.Logger;
import kafka.api.FetchRequest;
import kafka.api.FetchRequestBuilder;
import
.put("auto.offset.reset", "smallest");
props.put("socket.timeout.ms", "1");
Am i missing something ? Or this is a expected exception???
PS: We are using Java Client
Thanks in advance
Ranjith Venkatesan
