Assuming the configurations are as follows: max.inflight.requests.per.connection=1 enable.idempotence=false
Thanks, Nitin On Thu, Jan 28, 2021 at 1:53 PM nitin agarwal <nitingarg...@gmail.com> wrote: > Thanks for quick reply, I have understood this behaviour now. > I have another follow up question. > > Can the Source connector write out of order messages in a case where there > is a failure in committing the offset and the connector is restarted at the > same time? > > Thanks, > Nitin > > On Thu, Jan 28, 2021 at 8:06 AM Matthias J. Sax <mj...@apache.org> wrote: > >> There should not be any data loss. >> >> However, if a request fails and is retried, it may lead to reordering of >> sends. Thus, records would not be ordered based on the `send()` calls >> any longer. >> >> If you would enable idempotent writes, ordering is guaranteed even with >> multiple in-flight requests per connection though. >> >> >> >> -Matthias >> >> On 1/27/21 11:35 AM, nitin agarwal wrote: >> > Hi All, >> > >> > I see that max.inflight.requests.per.connection is set to 1 explicitly >> in >> > Kafka Connect but there is a way to override it. I want to understand >> the >> > impact of setting its value > 1. >> > As per my understanding, it will lead to data loss in some cases. Is it >> > correct ? >> > >> > >> > Thank you, >> > Nitin >> > >> >
