NDB Cluster Configuration Files 4208 The number of transactions closed by this replica. This value may be greater than the sum of Ndb_api_trans_commit_count_replica  and  Ndb_api_trans_abort_count_replica , since some transactions may have been rolled back. Although this variable can be read using either  SHOW GLOBAL STATUS  or  SHOW SESSION STATUS , it is effectively global in scope. If this MySQL server does not act as a replica, or does not use NDB tables, this value is always 0. For more information, see Section 23.5.13, “NDB API Statistics Counters and Variables” . The number of transactions closed by this MySQL Server (SQL node). This value may be greater than the sum of  Ndb_api_trans_commit_count  and  Ndb_api_trans_abort_count , since some transactions may have been rolled back. Although this variable can be read using either  SHOW GLOBAL STATUS  or  SHOW SESSION STATUS , it is effectively global in scope. For more information, see Section 23.5.13, “NDB API Statistics Counters and Variables” . The number of transactions committed in this client session. Although this variable can be read using either  SHOW GLOBAL STATUS  or  SHOW SESSION STATUS , it relates to the current session only, and is not affected by any other clients of this  mysqld . For more information, see Section 23.5.13, “NDB API Statistics Counters and Variables” . The number of transactions committed by this replica. Although this variable can be read using either  SHOW GLOBAL STATUS  or  SHOW SESSION STATUS , it is effectively global in scope. If this MySQL server does not act as a replica, or does not use NDB tables, this value is always 0. For more information, see Section 23.5.13, “NDB API Statistics Counters and Variables” . • Ndb_api_trans_commit_count_replica • Ndb_api_trans_commit_count_session • Ndb_api_trans_close_count • Ndb_api_trans_close_count_slave Note Deprecated in NDB 8.0.23; use  Ndb_api_trans_close_count_replica instead.