This problem was solved by upgrading from 0.10 to 0.11 (broker + client).
Thanks for your feedback.
On Thu, Nov 30, 2017 at 10:03 AM, Tom van den Berge <
tom.vandenbe...@gmail.com> wrote:
> The consumers are using default settings, which means that
> enable.auto.commit=true and auto.commit.inte
Can you also check if you have partition leaders flapping or changing rapidly?
Also, look at the following settings on your client configs:
max.partition.fetch.bytes
fetch.max.bytes
receive.buffer.bytes
We had a similar situation in our environment when the brokers were flooded
with data.
The sy
The consumers are using default settings, which means that
enable.auto.commit=true and auto.commit.interval.ms=5000. I'm not
committing manually; just consuming messages.
On Thu, Nov 30, 2017 at 1:09 AM, Frank Lyaruu wrote:
> Do you commit the received messages? Either by doing it manually or se
Do you commit the received messages? Either by doing it manually or setting
enable.auto.commit and auto.commit.interval.ms?
On Wed, Nov 29, 2017 at 11:15 PM, Tom van den Berge <
tom.vandenbe...@gmail.com> wrote:
> I'm using Kafka 0.10.0.
>
> I'm reading messages from a single topic (20 partitions
