Hi Ronak, Make sure you don’t have ATOMIC table updates within your transaction.
Thomas From: Stephen Darlington <sdarling...@apache.org> 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 opening attachments. 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 <ronak.malav.s...@gmail.com<mailto:ronak.malav.s...@gmail.com>> wrote: Ping again. Can someone answer please? - Ronak On Mon, Mar 18, 2024 at 12:04 PM Ronak Shah <ronak.malav.s...@gmail.com<mailto:ronak.malav.s...@gmail.com>> 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 even more time to holding up lock and creating snowball effect on queued up transactions before going in a completely dead state. I am wondering if it is safe to deadlock detection to be turned off by making IGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS to 0 Based on the guide, this detection is only for the bookkeeping and it is safe to turned off. Any guidance on that would be greatly appreciated. Ronak Please follow the hyperlink to important disclosures. https://www.dodgeandcox.com/disclosures/email_disclosure_funds.html
