Jason,
Setting request.required.acks=-1 is orthogonal to the 'at least once'
guarantee, it only relates to the latency/replication trade-off. For
example, even if you set request.required.acks to 1, and as long as you
retry on all non-fatal exceptions you have the "at least once" guarantee;
and ev
Guozhang,
It turns out this is not entirely true, you do need request.required.acks =
-1 (and yes, you need to retry if failure) in order have guaranteed
delivery.
I discovered this, when doing tests with rolling restarts (and hard
restarts) of the kafka servers. If the server goes down, e.g. if
Hi,
Is there an eta on the 0.8 Kafka Java API?
Is there a beta version that we can start playing with?
Thanks a lot.
Kieran
This email is confidential and subject to important disclaimers and conditions
including on offers for the purchase or sale of securities, accuracy and
completeness of
Hello Jason,
You are right. I think we just have different definitions about "at least
once". What you have described to me is more related to "availability",
which says that your message will not be lost when there are failures. And
we achieve this through replication (which is related to
request
Ok cool, thanks Jun :)
--
Felix
On Fri, Oct 25, 2013 at 11:34 PM, Jun Rao wrote:
> Yes, there won't be any feature development in 0.7.
>
> Thanks,
>
> Jun
>
>
> On Fri, Oct 25, 2013 at 6:32 PM, Felix GV wrote:
>
> > Hi guys,
> >
> > I don't see log.flush.interval being available on per-topic
