Closed AkshayAwate closed 8 months ago
It seems odd that the ProduceRequest are timing out after only one second, are you sure that you are not setting request.timeout.ms or message.timeout.ms?
@edenhill NO, I am not using request.timeout.ms or message.timeout.ms in my configs.
Ah, I think I see what is going on. Your produce rate is too high for the network/cluster causing messages to be queued in the client and when they're eventually transmitted their timeout might be so low that the message times out while in flight to the broker. Your run lasts for 303 seconds, the default message.timeout.ms is 300s, so that sort of makes sense.
If you reduce the producer queue size you will get quicker back pressure (produce() will raise QUEUE_FULL) and you can stop producing until there is room in the queue.
@edenhill okay, i will try with linger_ms=5 ?
No, rather limit queue.buffering.max.kbytes and queue.buffering.max.messages to only allow for say 60 seconds worth of messages. e.g., if your input rate is 1000 messages per second, set queue.buffering.max.messages to 60000.
@edenhill I will try and update.
@edenhill so main thing is i am using image bytes as payload.
Just wondering was the issue resolved, because I am facing something similar and wanted to ask if you ever found a resolution to this issue, thanks!
having the same problem. was this solved?
See my previous comments on setting queue sizes.
I have same issue.. how to solve this?
The main question is already answered by @edenhill. Closing this issue.
Description
I am doing some tests, first i sent 5 messages with payload of 1MB, then 50, 500 with same payload, it works well. But when i send 5k messages it throws error as :
My configs:
I have read max message payload can be 1MB, how to proceed for larger payload ? is there anything Iam missing ?
How to reproduce
Checklist
Please provide the following information:
confluent_kafka.version()
andconfluent_kafka.libversion()
): latest{...}
'debug': '..'
as necessary)