Also in addition to that how about generating event when updates are failed which can be listened to and custom logic can be added to handle the failures?
On Wed, Aug 29, 2018 at 6:56 AM, Denis Magda <dma...@apache.org> wrote: > Val, > > Sounds like a handy configuration option. I would allow setting a number of > retries. If the number is set to 0 then a failed update is discarded right > away. > > -- > Denis > > On Tue, Aug 28, 2018 at 9:14 PM Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Folks, > > > > Is there a way to limit or disable retries of failed updates in the > > write-behind store? I can't find one, it looks like if an update fails, > it > > is moved to the end of the queue and then eventually retried. If it fails > > again, process is repeated. > > > > Such behavior *might* be OK if failures are caused by database being > > temporarily unavailable. But what if update fails deterministically, for > > example due to a constraint violation? There is absolutely no reason to > > retry it, and at the same time it can cause stability and performance > > issues when buffer is full with such "broken" updates. > > > > Does it makes sense to add an option that would allow to limit number of > > retries (or even disable them)? > > > > -Val > > >
