Hi, Make sure that your code is not suspending these transactions under high load conditions. https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/transactions/Transaction.html#suspend--
See this guide: https://ignite.apache.org/docs/latest/key-value-api/transactions Try monitoring your transactions: sql views: https://ignite.apache.org/docs/latest/monitoring-metrics/system-views#transactions new metrics: https://ignite.apache.org/docs/latest/monitoring-metrics/metrics#monitoring-transactions jmx: https://ignite.apache.org/docs/latest/monitoring-metrics/new-metrics#transactions control script: https://ignite.apache.org/docs/latest/tools/control-script#transaction-management Check what configs you've set: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/TransactionConfiguration.html Are altering the topology, use one node only, and/or a memory only cluster. Simplify your code to make the transaction itself simpler. If all these steps fail, and you are able to create a reproducer, post it here, along w/the logs and the version #'s. Thanks, Alex -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
