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
