"Local: Message timed out" and message loss

[alexec]

Read the FAQ first: https://github.com/edenhill/librdkafka/wiki/FAQ

Do NOT create issues for questions, use the discussion forum: https://github.com/edenhill/librdkafka/discussions

Description

When using enable.idempotence=true , I get this error occasionally (typically 10k incidents. All the messages are lost. retries=MAXINT32 does not seem to be honoured. librdkafka just seems to give up. I think this happens when connection to Kafka is lost.

Do I need to set message.timeout.ms=MAXINT32 as well?

https://github.com/argoproj-labs/argo-dataflow/issues/509

How to reproduce

<your steps how to reproduce goes here, or remove section if not relevant>

I'm sorry. All I know is that this happens every few days.

IMPORTANT: Always try to reproduce the issue on the latest released version (see https://github.com/edenhill/librdkafka/releases), if it can't be reproduced on the latest version the issue has been fixed.

Checklist

IMPORTANT: We will close issues where the checklist has not been completed.

Please provide the following information:

• [x] librdkafka version (release number or git tag): <REPLACE with e.g., v0.10.5 or a git sha. NOT "latest" or "current">
• [ ] Apache Kafka version: <REPLACE with e.g., 0.10.2.3>
• [ ] librdkafka client configuration: <REPLACE with e.g., message.timeout.ms=123, auto.reset.offset=earliest, ..>
• [ ] Operating system: <REPLACE with e.g., Centos 5 (x64)>
• [ ] Provide logs (with debug=.. as necessary) from librdkafka
• [ ] Provide broker log excerpts
• [ ] Critical issue