Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
0.9.0.0
-
None
-
None
Description
When broker was sending a FetchResponse it is possible that the data to be sent back is truncated. In this case, a KafkaException will be thrown. This exception is caught by processor and the selector will be sending the message in a tight while loop. It will continue doing this until the socket is closed by the client due to request timeout.
We should have a max retry for the response send.
Attachments
Issue Links
- relates to
-
KAFKA-2978 Topic partition is not sometimes consumed after rebalancing of consumer group
- Resolved