Hi Ronak,
Make sure you don’t have ATOMIC table updates within your transaction.
Thomas
From: Stephen Darlington
Sent: Monday, March 25, 2024 2:31 AM
To: user@ignite.apache.org
Subject: Re: Turning off deadlock detection
This is an EXTERNAL EMAIL. Stop and think before clicking a link or
Just a reminder that this list is run by volunteers. If you need responses
in a given time, commercial options are available.
On Sat, 23 Mar 2024 at 17:50, Ronak Shah wrote:
> Ping again. Can someone answer please? - Ronak
>
> On Mon, Mar 18, 2024 at 12:04 PM Ronak Shah
> wrote:
>
>> Hi Ignite
Thanks Jeremy for the reply. Why does deadlock detection pause all other transaction though for a min? Shouldnt it be a low priority thread job compared to db transactions?RonakOn Mar 24, 2024, at 8:52 PM, Jeremy McMillan wrote:https://ignite.apache.org/docs/latest/key-value-api/transactions#dead
https://ignite.apache.org/docs/latest/key-value-api/transactions#deadlock-detection
The property you're asking about is for diagnostics to enable prevention of
future deadlocks. Turning it off is fine if you already know or can find
out another way what is deadlocked and why.
On Sat, Mar 23, 2024
Ping again. Can someone answer please? - Ronak
On Mon, Mar 18, 2024 at 12:04 PM Ronak Shah
wrote:
> Hi Ignite users,
> I am hitting a situation in a scaled environment where if the transaction
> timeouts for whatever reason, the cluster goes in a deadlock detection
> mode, where it is taking eve
Hi Ignite users,
I am hitting a situation in a scaled environment where if the transaction
timeouts for whatever reason, the cluster goes in a deadlock detection
mode, where it is taking even more time to holding up lock and creating
snowball effect on queued up transactions before going in a compl
