Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
0.10.1.0
-
None
-
None
Description
In the new mirror maker (like the old MM), the MM asynchronously sends data through the producer. Due to this, it doesn't have a way to get any exception that the producer sends back and do something meaningful. At least not without falling back to synchronous behavior. What this means is that if the producer runs out of retries, it silently drops data on the floor and the user is left wondering why the # of messages in the target cluster don't match with those in the source cluster.
Attachments
Issue Links
- is duplicated by
-
KAFKA-1302 cleanup logging in new producer
- Resolved