you got it right... But DialTimeout is not a concern here. Client try fetching metadata from Kafka brokers but Kafka give them stale metadata near 30-40 sec. It try to fetch 3-4 time in between until it get updated metadata. This is completely different problem than https://github.com/Shopify/sarama/issues/661
On Thu, Jun 2, 2016 at 6:05 PM, Steve Tian <steve.cs.t...@gmail.com> wrote: > So you are coming from https://github.com/Shopify/sarama/issues/661 , > right? I'm not sure if anything from broker side can help but looks like > you already found DialTimeout on client side can help? > > Cheers, Steve > > On Fri, Jun 3, 2016, 8:33 AM safique ahemad <saf.jnu...@gmail.com> wrote: > > > kafka version:0.9.0.0 > > go sarama client version: 1.8 > > > > On Thu, Jun 2, 2016 at 5:14 PM, Steve Tian <steve.cs.t...@gmail.com> > > wrote: > > > > > Client version? > > > > > > On Fri, Jun 3, 2016, 4:44 AM safique ahemad <saf.jnu...@gmail.com> > > wrote: > > > > > > > Hi All, > > > > > > > > We are using Kafka broker cluster in our data center. > > > > Recently, It is realized that when a Kafka broker goes down then > client > > > try > > > > to refresh the metadata but it get stale metadata upto near 30 > seconds. > > > > > > > > After near 30-35 seconds, updated metadata is obtained by client. > This > > is > > > > really a 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 > > > > > > > > > > > > > > > -- > > > > Regards, > > Safique Ahemad > > GlobalLogic | Leaders in software R&D services > > P :+91 120 4342000-2990 | M:+91 9953533367 > > www.globallogic.com > > > -- Regards, Safique Ahemad GlobalLogic | Leaders in software R&D services P :+91 120 4342000-2990 | M:+91 9953533367 www.globallogic.com
