NDB Cluster Configuration Files • Ndb_api_wait_scan_result_count The number of times a thread has been blocked by this MySQL Server (SQL node) while waiting for a scan-based signal, such as when waiting for more results from a scan, or when waiting for a scan to close. 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” . • Ndb_cluster_node_id If the server is acting as an NDB Cluster node, then the value of this variable its node ID in the cluster. If the server is not part of an NDB Cluster, then the value of this variable is 0. • Ndb_config_from_host If the server is part of an NDB Cluster, the value of this variable is the host name or IP address of the Cluster management server from which it gets its configuration data. If the server is not part of an NDB Cluster, then the value of this variable is an empty string. • Ndb_config_from_port Shows the generation number of the cluster’s current configuration. This can be used as an indicator to determine whether the configuration of the cluster has changed since this SQL node last connected to the cluster. If the server is part of an NDB Cluster, the value of this variable is the number of the port through which it is connected to the Cluster management server from which it gets its configuration data. If the server is not part of an NDB Cluster, then the value of this variable is 0. • Ndb_config_generation • Ndb_conflict_fn_max_del_win Shows the number of times that a row was rejected on the current SQL node due to NDB Cluster Replication conflict resolution using  NDB$MAX_DELETE_WIN() , since the last time that this  mysqld  was started. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . • Ndb_conflict_fn_max Used in NDB Cluster Replication conflict resolution, this variable shows the number of times that a row was not applied on the current SQL node due to “greatest timestamp wins”  conflict resolution since the last time that this  mysqld  was started. For more information, see Section 23.6.11, “NDB Cluster Replication Conflict Resolution” . • Ndb_conflict_fn_old Used in NDB Cluster Replication conflict resolution, this variable shows the number of times that a row was not applied as the result of “same timestamp wins”  conflict resolution on a given  mysqld  since the last time it was restarted. 4215