Thank you for reply, Neha Kafka executes the reconnecting logic as 'reconnect.time.interval.ms' property after running 'send.writeCompletely(channel)' (See, 'send' method in SyncProducer.scala (88th line))
An exception occurs at SocketChannel.write (at BoundedByteBufferSend.writeTo) So, I'll meet the problem regardless of 'reconnect.time.interval.ms' value. ps. I think the reconnection logic should be placed before sending a message... in the getOrMakeConnection() method which has a reponsibility to manage connection. On Mon, Sep 23, 2013 at 11:17 PM, Neha Narkhede <[email protected]>wrote: > You can configure the producer to reconnect to the brokers and set the > reconnect interval to less than an hour. The config that controls this is > reconnect.time.interval.ms. > > Thanks, > Neha > On Sep 23, 2013 12:14 AM, "Rhapsody" <[email protected]> wrote: > > > Hi everyone, > > I'm using Kafka 0.7.2 > > > > My firewall forcely close the tcp session > > when it's no transmission btw two end points for one hour. > > > > When a producer in that network dosen't send any message to Kafka broker > > for one hour, > > it makes problem. > > > > I can't touch that firewall configuration. > > > > Alternatively, I can send dummy logs to kafka, and ignore them in > consumer. > > However, I don't think it to be a good way to handle architecural issues > in > > bussiness logic. > > > > Does anyone have good idea? > > (Actually, I hope Kafka supports heartbeat feature.) > > > > > > Thanks, > > > > Cnulwoo Choi > > >
