=100
---
We actually play around request.required.acks in producer config, -1
cause
long latency, 1 is the parameter to cause messages lost. But I am not
sure,
if this is the reason to lose the records.
thanks
AL
On Fri, Jan 2, 2015
request.required.acks in producer config, -1
cause
long latency, 1 is the parameter to cause messages lost. But I am not
sure,
if this is the reason to lose the records.
thanks
AL
On Fri, Jan 2, 2015 at 9:59 AM, Timothy Chen tnac...@gmail.com
wrote
play around request.required.acks in producer config, -1
cause
long latency, 1 is the parameter to cause messages lost. But I am not
sure,
if this is the reason to lose the records.
thanks
AL
On Fri, Jan 2, 2015 at 9:59 AM, Timothy Chen tnac...@gmail.com
request.required.acks in producer config, -1 cause
long latency, 1 is the parameter to cause messages lost. But I am not sure,
if this is the reason to lose the records.
thanks
AL
On Fri, Jan 2, 2015 at 9:59 AM, Timothy Chen tnac...@gmail.com wrote:
What's your configured required.acks
:2181,10.100.70.29:2181
zookeeper.connection.timeout.ms=100
---
We actually play around request.required.acks in producer config, -1 cause
long latency, 1 is the parameter to cause messages lost. But I am not sure,
if this is the reason to lose the records.
thanks
AL
On Fri, Jan
What's your configured required.acks? And also are you waiting for all
your messages to be acknowledged as well?
The new producer returns futures back, but you still need to wait for
the futures to complete.
Tim
On Fri, Jan 2, 2015 at 9:54 AM, Sa Li sal...@gmail.com wrote:
Hi, all
We are
Hi, all
We are sending the message from a producer, we send 10 records, but we
see only 99573 records for that topics, we confirm this by consume this
topic and check the log size in kafka web console.
Any ideas for the message lost, what is the reason to cause this?
thanks
--
Alec Li
