pany policy. This is a big risk for our operation as all our
> servers
> at one data center must be rebooted regularly at the same time by system
> admins.
> So rolling start is not an option for us.
>
> > Date: Sat, 7 Jun 2014 16:02:35 -0700
> > Subject: Re: ques
same time by system admins.
So rolling start is not an option for us.
> Date: Sat, 7 Jun 2014 16:02:35 -0700
> Subject: Re: question about synchronous producer
> From: wangg...@gmail.com
> To: users@kafka.apache.org
>
> I see. So previously you run the test as ack=1?
>
> G
fka code and no exception has been thrown.
>
> I did a new test with request.required.acks set to -1. The number of lost
> message dropped significantly but there were still message loss.
>
> > Date: Fri, 6 Jun 2014 08:12:17 -0700
> > Subject: Re: question about synchronous produ
significantly but there were still message loss.
> Date: Fri, 6 Jun 2014 08:12:17 -0700
> Subject: Re: question about synchronous producer
> From: wangg...@gmail.com
> To: users@kafka.apache.org
>
> Libo,
>
> I have double checked the code. With sync producers all failures s
ge
> > > loss after 3 restarts. After 3 restarts, I use a consumer to retrieve
> the
> > > messages and do the verification.
> > >
> > > > Date: Thu, 5 Jun 2014 10:15:18 -0700
> > > > Subject: Re: question about synchronous produc
time.
> Date: Thu, 5 Jun 2014 16:53:29 -0700
> Subject: Re: question about synchronous producer
> From: wangg...@gmail.com
> To: users@kafka.apache.org
>
> Libo, did you see any exception/error entries on the producer log?
>
> Guozhang
>
>
> On Thu, Jun 5,
processes ( 3 hosts in a cluster). Normally there will be message
> loss after 3 restarts. After 3 restarts, I use a consumer to retrieve the
> messages and do the verification.
>
> > Date: Thu, 5 Jun 2014 10:15:18 -0700
> > Subject: Re: question about synchronous producer
>
messages and do
the verification.
> Date: Thu, 5 Jun 2014 10:15:18 -0700
> Subject: Re: question about synchronous producer
> From: wangg...@gmail.com
> To: users@kafka.apache.org
>
> Libo,
>
> For clarification, you can use sync producer to reproduce this issue?
>
>
s are restarted during
> publishing. It
> > > is a sync producer with request.required.acks set to 1.
> > >
> > > Libo
> > >
> > > > Date: Thu, 29 May 2014 20:11:48 -0700
> > > > Subject: Re: question about synchronous producer
> > &g
is 0.8.0. It is
fairly easy to reproduce. Any insight on this issue?
Libo
> Date: Thu, 5 Jun 2014 09:05:27 -0700
> Subject: Re: question about synchronous producer
> From: wangg...@gmail.com
> To: users@kafka.apache.org
>
> When the producer exhausted all the retries it will d
o long.
> I've noticed message loss when brokers are restarted during publishing. It
> is a sync producer with request.required.acks set to 1.
>
> Libo
>
> > Date: Thu, 29 May 2014 20:11:48 -0700
> > Subject: Re: question about synchronous producer
> > From: wangg
I want to know why there will be message loss when brokers are down for too
long.
I've noticed message loss when brokers are restarted during publishing. It is a
sync producer with request.required.acks set to 1.
Libo
> Date: Thu, 29 May 2014 20:11:48 -0700
> Subject: Re: que
nd() is being called, if brokers are down, send will throw
>> FailedToSendMessageException. Users can catch it and retry.
>>
>> > From: yu_l...@hotmail.com
>> > To: users@kafka.apache.org
>> > Subject: RE: question about synchronous producer
>> > Date:
n. Users can catch it and retry.
>
> > From: yu_l...@hotmail.com
> > To: users@kafka.apache.org
> > Subject: RE: question about synchronous producer
> > Date: Fri, 30 May 2014 08:32:44 -0400
> >
> > Thanks for your help, Guozhen.
> > Assume request.requir
he.org
> Subject: RE: question about synchronous producer
> Date: Fri, 30 May 2014 08:32:44 -0400
>
> Thanks for your help, Guozhen.
> Assume request.required.acks is set to 1 for the scenario I mentioned.
> While send() is being called, brokers are shutdown. What should I
.
Thanks,
Libo
> Date: Thu, 29 May 2014 20:11:48 -0700
> Subject: Re: question about synchronous producer
> From: wangg...@gmail.com
> To: users@kafka.apache.org
>
> Libo,
>
> That is correct. You may want to increase the retry.backoff.ms in this
> case. In practice,
Libo,
That is correct. You may want to increase the retry.backoff.ms in this
case. In practice, if the brokers are down for too long, then data loss is
usually inevitable.
Guozhang
On Thu, May 29, 2014 at 2:55 PM, Libo Yu wrote:
> Hi team,
>
> Assume I am using a synchronous producer and it h
17 matches
Mail list logo
