then that should not make a difference.
I am not sure, if is right behavior?
Please, suggest.
--
Regards,
Safique Ahemad
I digged it furthermore...
It seems the API blockingSendAndReceive hanging for a long to send/receive
response from the broker which is not affected.
I just checked send and receive time its taking near about 30 sec.
On Tue, Jun 14, 2016 at 11:03 AM, safique ahemad
wrote:
> Guys
roducer/consumers in a dockerized setup, there where only few
> > failures before the producer switched to to correct new broker again. I
> > don't know the exact time, but seemed like a few seconds at max, this was
> > with with 0.9.0.0.
> >
> > On
; brokers/topics setup and the steps to reproduce this issue?
>
> Cheers, Steve
>
> On Fri, Jun 3, 2016, 9:45 AM safique ahemad wrote:
>
> > you got it right...
> >
> > But DialTimeout is not a concern here. Client try fetching metadata from
> > Kafka brokers bu
Cheers, Steve
>
> On Fri, Jun 3, 2016, 8:33 AM safique ahemad wrote:
>
> > kafka version:0.9.0.0
> > go sarama client version: 1.8
> >
> > On Thu, Jun 2, 2016 at 5:14 PM, Steve Tian
> > wrote:
> >
> > > Client version?
> > >
kafka version:0.9.0.0
go sarama client version: 1.8
On Thu, Jun 2, 2016 at 5:14 PM, Steve Tian wrote:
> Client version?
>
> On Fri, Jun 3, 2016, 4:44 AM safique ahemad wrote:
>
> > Hi All,
> >
> > We are using Kafka broker cluster in our data center.
> >
large time for the client continuously gets send failure for so
long.
Kindly, reply if any configuration may help here or something else or
required.
--
Regards,
Safique Ahemad
