I am observing the following warnings in logs:
08:28:20 [Warn ] [KAFKA_PRODUCER] [anonymous] [5] [REQTMOUT] [thrd:sasl_plaintext://kafka1:9093/1]: sasl_plaintext://kafka1:9093/1: Timed out MetadataRequest in flight (after 60659ms, timeout #0)
08:28:20 [Warn ] [KAFKA_PRODUCER] [anonymous] [4] [REQTMOUT] [thrd:sasl_plaintext://kafka1:9093/1]: sasl_plaintext://kafka1:9093/1: Timed out 1 in-flight, 0 retry-queued, 0 out-queue, 0 partially-sent requests
which effectively results in error callback being called with code -185 and reason sasl_plaintext://kafka1:9093/1: 1 request(s) timed out: disconnect (after 907686ms in state UP)
.
I see similar errors for ProduceRequest as well.
I have modified the configuration to 'debug=protocol' to get more detailed logs and be able to trace particular requests that time out.
I have a few questions around that:
debug=protocol
the right setting to get more information about this issue?ProduceRequest
, will I loose data?socker.timeout.ms
safe to do here as a remediation?Let me know if providing more details would help to answer the questions. Thank you.
How to reproduceNo way of consistent reproduction found.
ChecklistIMPORTANT: We will close issues where the checklist has not been completed.
Please provide the following information:
v1.0.0
2.1
<Config name="message.timeout.ms" value="300000" />
<Config name="enable.idempotence" value="true" />
<Config name="linger.ms" value="500" />
<Config name="compression.codec" value="snappy" />
<Config name="batch.num.messages" value="100000" />
<Config name="retry.backoff.ms" value="500" />
Centos 7 (x64)>
debug=..
as necessary) from librdkafka - waiting for reproduction with 'debug=protocol'RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4