I you set `enable.idempotence=true`, the producer will retry internally.
Thus, it should never throw an retriable exception in the first place
(so there is nothing to ignore :)).
-Matthias
On 7/2/17 6:28 PM, Gary Struthers wrote:
> I currently catch and retry Retriable exceptions. The v11 docs s
I currently catch and retry Retriable exceptions. The v11 docs say if
enable.idempotence=true than my application shouldn’t retry if these exceptions
are thrown because my retries wouldn’t be idempotent. Am I supposed to ignore
these exceptions now? I use the Java driver.
Gary
When you write the msg results to MySQL, you include the offset of the message
with the results. This can be done in one atomic write transaction. Then if
your application crashes, when it starts back up, it should read the offset
stored with the last message results in the database, then seek()
