NDB Cluster Configuration Files See Section 23.6.11, “NDB Cluster Replication Conflict Resolution” , for more information. Number of rows found to be in conflict by a transactional conflict function See Section 23.6.11, “NDB Cluster Replication Conflict Resolution” , for more information. Used in NDB Cluster Replication conflict resolution, this status variable shows the number of rows found to be directly in-conflict by a transactional conflict function on a given  mysqld  since the last time it was restarted. Currently, the only transactional conflict detection function supported by NDB Cluster is NDB$EPOCH_TRANS(), so this status variable is effectively the same as Ndb_conflict_fn_epoch_trans . For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Used in NDB Cluster Replication conflict resolution, this status variable shows the total number of rows realigned due to being determined as conflicting by a transactional conflict detection function. This includes not only  Ndb_conflict_trans_row_conflict_count , but any rows in or dependent on conflicting transactions. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Used in NDB Cluster Replication conflict resolution, this status variable shows the number of transactions found to be in conflict by a transactional conflict detection function. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Used in NDB Cluster Replication conflict resolution, this shows the number of internal iterations required to commit an epoch transaction. Should be (slightly) greater than or equal to Ndb_conflict_trans_conflict_commit_count . For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Used in NDB Cluster Replication conflict resolution, this shows the number of epoch transactions committed after they required transactional conflict handling. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . When using delete-delete conflict detection, this is the number of delete-delete conflicts detected, where a delete operation is applied, but the indicated row does not exist. 4217 • Ndb_execute_count • Ndb_epoch_delete_delete_count • Ndb_conflict_trans_conflict_commit_count • Ndb_conflict_trans_detect_iter_count • Ndb_conflict_trans_reject_count • Ndb_conflict_trans_row_reject_count • Ndb_conflict_trans_row_conflict_count • Ndb_conflict_last_stable_epoch