Major Currently, RecordCollectorImpl implements an internal retry loop for sending data with a hard coded retry maximum. This raises the problem, that data might be send out-of-order while at the same time, does not improve the overall resilience much, as the number of retires is hardcoded.
Thus, we should remove this loop and only rely an producer configuration parameter retires that uses can configure accordingly.
- links to
