Re: Why fetching meta-data for topic is done three times?

Hi Zakee, Yes even if retries is set to 1 it takes 3 sec to throw an exception. I am not sure in producer code whether they intentionally swallowing all exception while doing send which internally does 3 tasks. If 1st itself get failed whether to proceed for next is required? Now for throwing exc

Re: Why fetching meta-data for topic is done three times?

With reties 1 you still see the 3 secs delay? The idea is, you can change these property to reduce the time to throw exception to 1 secs or below. Does that help? Thanks Zakee > On Apr 28, 2015, at 10:29 PM, Madhukar Bharti > wrote: > > Hi Zakee, > >> message.send.max.retries is 1 > > Re

Re: Why fetching meta-data for topic is done three times?

Hi Zakee, >message.send.max.retries is 1 Regards, Madhukar On Tue, Apr 28, 2015 at 6:17 PM, Madhukar Bharti wrote: > Hi Zakee, > > Thanks for your reply. > > >message.send.max.retries > 3 > > >retry.backoff.ms > 100 > > >topic.metadata.refresh.interval.ms > 600*1000 > > This is my properties.

Re: Why fetching meta-data for topic is done three times?

Hi Zakee, Thanks for your reply. >message.send.max.retries 3 >retry.backoff.ms 100 >topic.metadata.refresh.interval.ms 600*1000 This is my properties. Regards, Madhukar On Tue, Apr 28, 2015 at 3:26 AM, Zakee wrote: > What values do you have for below properties? Or are these set to default

Re: Why fetching meta-data for topic is done three times?

What values do you have for below properties? Or are these set to defaults? message.send.max.retries retry.backoff.ms topic.metadata.refresh.interval.ms Thanks Zakee > On Apr 23, 2015, at 11:48 PM, Madhukar Bharti > wrote: > > Hi All, > > Once gone through code found that, While Producer s

Re: Why fetching meta-data for topic is done three times?

Hi All, Once gone through code found that, While Producer starts it does three things: 1. Sends Meta-data request 2. Send message to broker(fetching broker list) 3. If number of message to be produce is grater than 0 then again tries to refresh metadata for outstanding produce requests. Each of

Why fetching meta-data for topic is done three times?

Hi All, I came across a problem, If we use broker IP which is not reachable or out of network. Then it takes more than configured time(request.timeout.ms). After checking the log got to know that it is trying to fetch topic meta-data three times by changing correlation id. Due to this even though