eG Help

Transactions allows to group multiple cache operations, on one or more keys, into a single atomic transaction. These operations are executed without any other interleaved operations on the specified keys, and either all succeed or all fail. There is no partial execution of the operations. Transactions can be enabled for a specific cache in the cache configuration.

Transaction management is one of the key features of any database, the more robust the transactions management, the better the database maintains the data integrity. Given that Apache Ignite is a distributed and cache based database, it makes transaction management even more difficult and prone to problems. That's the reason it is absolutely important to monitor the cache transactions to be sure that operation initiated re successful. Though Apache Ignite can be relied on to maintain the sanctity of transaction, administrators must ensure that tasks and jobs are succeeding are not blocked because of failed transactions.

This test monitors Apache Ignite cluster to gather transactions related statistics and provide key information to administrators about transactions success rate.

Measurement	Description	Measurement Unit	Interpretation
lockedKeys	Indicates the total number of key locked on the node i.e. which are under a transaction and cannot be updated.	Number	If there are too many keys locked on the node, no other operation can be performed until these keys are released, and at times can lead to deadlock.
transactionsCommitted	Indicates the total number of transactions committed on the node ever since the cluster is started.	Number
transactionsRolledBack	Indicates the total number of transactions which were rolled back ever since the cluster is started.	Number	Out of total number of transactions, if the number of rolled back transactions is high, administrators need to investigate why system is not able to complete the transactions.
ownerTransactions	Indicates the total number of transactions that were initiated on the node ever since the cluster is started.	Number
transactionsHoldingLock	Indicates the total number of open transactions which are still holding lock on at least one of the keys on the node.	Number	If there are too many keys locked on the node, no other operation can be performed until these keys are released, and at times can lead to deadlock.