RE: Kafka client circuit breaker

2016-10-31 Thread Tauzell, Dave
---Original Message- From: Andrey Dyachkov [mailto:andrey.dyach...@gmail.com] Sent: Monday, October 31, 2016 3:17 AM To: users@kafka.apache.org Subject: Re: Kafka client circuit breaker R Krishna, A particular set of exceptions has to be defined. At least what I know: timeout exception, netwo

Re: Kafka client circuit breaker

2016-10-31 Thread Andrey Dyachkov
R Krishna, A particular set of exceptions has to be defined. At least what I know: timeout exception, network exception. I am not sure I got the point about auto-recovery. About incoming messages, we can return the exception that the client can not access topic/broker/partition and user can properl

Re: Kafka client circuit breaker

2016-10-30 Thread Tauzell, Dave
Once enough failures happen the circuit is marked open. The client would then periodically try some messages until it works again. Others would be failed. There are a number of existing circuit breaker libraries you can use in the meantime like the Netflix one. Dave > On Oct 30, 2016, at 20:

Re: Kafka client circuit breaker

2016-10-30 Thread R Krishna
So, basically, you want the clients to gracefully handle timeouts and short circuit if it is unavailable broker exception and also clients should be able automatically recover when it is up? What about the messages that come in when broker is not available? On Sun, Oct 30, 2016 at 12:25 PM, Andrey

Re: Kafka client circuit breaker

2016-10-30 Thread Andrey Dyachkov
R Krishna, We have default timeout for producer and consumer it is 30 secs. If Kafka is not available we will wait 30 secs on each request. Decreasing timeout won't help much because we have a lot requests but circuiting them will help us tremendous. We could implement such logic before actually c

Re: Kafka client circuit breaker

2016-10-29 Thread R Krishna
What are the issues and problems you want to solve though? On Oct 29, 2016 3:59 AM, "Andrey Dyachkov" wrote: > Hi, > > We use Kafka for around half a year as a main backend system for storing > events from big variety of internal microservices. In general It works > quite well and we experience i