https://issues.apache.org/jira/browse/IGNITE-13064 is raised with label "newbie".
On Tue, May 19, 2020 at 4:10 PM Ivan Rakov <ivan.glu...@gmail.com> wrote: > Support this idea in general but why 5 minutes and not less? > > This value looks to me greater than any value that can possibly affect > existing deployments (existing long transactions may suddenly start to > rollback), but less than reaction time of users that are only starting to > get along with Ignite and suddenly experience TX deadlock. > > -- > Best Regards, > Ivan Rakov > > On Tue, May 19, 2020 at 10:31 AM Anton Vinogradov <a...@apache.org> wrote: > >> +1 >> >> On Mon, May 18, 2020 at 9:45 PM Sergey Antonov <antonovserge...@gmail.com >> > >> wrote: >> >> > +1 >> > >> > пн, 18 мая 2020 г. в 21:26, Andrey Mashenkov < >> andrey.mashen...@gmail.com>: >> > >> > > +1 >> > > >> > > On Mon, May 18, 2020 at 9:19 PM Ivan Rakov <ivan.glu...@gmail.com> >> > wrote: >> > > >> > > > Hi Igniters, >> > > > >> > > > I have a very simple proposal. Let's set default TX timeout to 5 >> > minutes >> > > > (right now it's 0 = no timeout). >> > > > Pros: >> > > > 1. Deadlock detection procedure is triggered on timeout. In case >> user >> > > will >> > > > get into key-level deadlock, he'll be able to discover root cause >> from >> > > the >> > > > logs (even though load will hang for a while) and skip step with >> > googling >> > > > and debugging. >> > > > 2. Almost every system with transactions has timeout enabled by >> > default. >> > > > >> > > > WDYT? >> > > > >> > > > -- >> > > > Best Regards, >> > > > Ivan Rakov >> > > > >> > > >> > > >> > > -- >> > > Best regards, >> > > Andrey V. Mashenkov >> > > >> > >> > >> > -- >> > BR, Sergey Antonov >> > >> >
