The root of problem is consumer lag on one or two partition even with no op
( read log and discard it) consumer . Our use case is very simple. Send
all the log lines to Brokers. But under storm of data (due to exception or
application error etc), one or two partition gets lags behind while
In the new producer, a client can specify the partition number for each
message. Then, any partitioning strategy can be implemented by the client.
Thanks,
Jun
On Thu, Aug 7, 2014 at 1:37 PM, Bhavesh Mistry mistry.p.bhav...@gmail.com
wrote:
The root of problem is consumer lag on one or two
Bhavesh, take a look at
https://cwiki.apache.org/confluence/display/KAFKA/FAQ#FAQ-Whyisdatanotevenlydistributedamongpartitionswhenapartitioningkeyisnotspecified
?
Maybe the root cause issue is something else? Even if producers produce
more or less than what they are producing you should be able
