In Kafka, we detect failures using ZK. So, if the network connectivity btw
the producer and the broker is down, but the one btw the broker and ZK is
up, we assume the broker is still alive and will continue to send the data
to it. Within the the same data center, we assume this is extremely rare.
I
The goal is to use sync producer and find out that network is down as
soon as possible.
--
Viktor
2013/8/13 Viktor Kolodrevskiy :
> Felix,
> the thing is that I was using sync producer.
>
> --
> Viktor
>
> 2013/8/13 Felix GV :
>> Async production is meant to work this way. You have no delivery gu
Felix,
the thing is that I was using sync producer.
--
Viktor
2013/8/13 Felix GV :
> Async production is meant to work this way. You have no delivery guarantee
> nor any exception because the producer sends the message independently of
> the code that called the aync production function.
>
> It i
Async production is meant to work this way. You have no delivery guarantee
nor any exception because the producer sends the message independently of
the code that called the aync production function.
It is meant to be faster than sync production, but it is obviously intended
for non-critical messa
Hey guys,
We decided to use Kafka in our new project, now I spend some time to
research how Kafka producer behaves while network connectivity
problems.
I had 3 virtual machines(ubuntu 13.04, running on Virtualbox) in one network:
1. Kafka server(0.7.2) + Zookeper.
2. Producer app with default se
