Ricardo,
Thanks for your response. I've been looking over your advice and examining the
Kafka client code and our logs. I'm still thinking that the issue is simply
that the Broker can't keep up with the offset commit rate. The reasons for
this are:
* The first message in any sequence is
"o
James,
If I were you I would start investigating what is causing this network
drops between your cluster and your consumers. The following messages
are some indications of this:
* "Offset commit failed on partition MyTopic-53 at offset 957: The
request *timed out*."
* "Caused by: org.apach
We are using AWS MSK with Kafka 2.4.1 (and same client version), 3 Brokers. We
are seeing fairly frequent consumer offset commit fails as shown in the example
logs below. Things continue working as they are all retriable, however I would
like to improve this situation.
The issue occurs most o
