NDB Cluster Configuration Files For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Used in NDB Cluster Replication conflict resolution, this variable shows the number of rows found to be in conflict using  NDB$EPOCH()  conflict resolution on a given  mysqld  since the last time it was restarted. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Shows the number of rows found to be in conflict in NDB Cluster Replication conflict resolution, when using  NDB$EPOCH2() , on the source designated as the primary since the last time it was restarted. For more information, see NDB$EPOCH2(). Used in NDB Cluster Replication conflict resolution, this variable shows the number of rows found to be in conflict using  NDB$EPOCH_TRANS()  conflict resolution on a given  mysqld  since the last time it was restarted. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . Used in NDB Cluster Replication conflict resolution, this variable shows the number of rows found to be in conflict using  NDB$EPOCH_TRANS2()  conflict resolution on a given  mysqld  since the last time it was restarted. For more information, see NDB$EPOCH2_TRANS(). The most recent epoch in which a conflict was detected on this replica. You can compare this value with Ndb_replica_max_replicated_epoch ; if  Ndb_replica_max_replicated_epoch  is greater than  Ndb_conflict_last_conflict_epoch , no conflicts have yet been detected. See Section 23.6.11, “NDB Cluster Replication Conflict Resolution” , for more information. When using NDB Cluster Replication conflict resolution, this is the number of reflected operations that were not applied on the secondary, due to encountering an error during execution. See Section 23.6.11, “NDB Cluster Replication Conflict Resolution” , for more information. When using conflict resolution with NDB Cluster Replication, this status variable contains the number of reflected operations that have been defined (that is, prepared for execution on the secondary). See Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . When using conflict resolution with NDB Cluster Replication, this gives the number of refresh operations that have been prepared for execution on the secondary. 4216 • Ndb_conflict_fn_epoch • Ndb_conflict_fn_epoch2 • Ndb_conflict_fn_epoch_trans • Ndb_conflict_fn_epoch2_trans • Ndb_conflict_last_conflict_epoch • Ndb_conflict_reflected_op_discard_count • Ndb_conflict_reflected_op_prepare_count • Ndb_conflict_refresh_op_count