Overview of NDB Cluster Configuration Parameters, Options, and Variables • ndb_autoincrement_prefetch_sz : NDB auto-increment prefetch size. • ndb_cache_check_time : Number of milliseconds between checks of cluster SQL nodes made by MySQL query cache. • ndb_clear_apply_status : Causes RESET SLAVE/RESET REPLICA to clear all rows from ndb_apply_status table; ON by default. • Ndb_cluster_node_id : Node ID of this server when acting as NDB Cluster SQL node. • Ndb_config_from_host : NDB Cluster management server host name or IP address. • Ndb_config_from_port : Port for connecting to NDB Cluster management server. • Ndb_config_generation : Generation number of the current configuration of the cluster. • Ndb_conflict_fn_epoch : Number of rows that have been found in conflict by NDB$EPOCH() conflict detection function. • Ndb_conflict_fn_epoch2 : Number of rows that have been found in conflict by NDB$EPOCH2() conflict detection function. • Ndb_conflict_fn_epoch2_trans : Number of rows that have been found in conflict by NDB $EPOCH2_TRANS() conflict detection function. • Ndb_conflict_fn_epoch_trans : Number of rows that have been found in conflict by NDB $EPOCH_TRANS() conflict detection function. • Ndb_conflict_fn_max : Number of times that conflict resolution based on "greater timestamp wins" has been applied when server is part of an NDB Cluster involved in cluster replication. • Ndb_conflict_fn_old : Number of times that "same timestamp wins" conflict resolution has been applied when this server is part of an NDB Cluster involved in cluster replication. • Ndb_conflict_last_conflict_epoch : Most recent NDB epoch on this replica in which some conflict was detected. • Ndb_conflict_last_stable_epoch : Number of rows found to be in conflict by transactional conflict function. • Ndb_conflict_reflected_op_discard_count : Number of reflected operations that were not applied due error during execution. • Ndb_conflict_reflected_op_prepare_count : Number of reflected operations received that have been prepared for execution. • Ndb_conflict_refresh_op_count : Number of refresh operations that have been prepared. • ndb_conflict_role : Role for replica to play in conflict detection and resolution. Value is one of PRIMARY, SECONDARY, PASS, or NONE (default). Can be changed only when replication SQL thread is stopped. See documentation for further information. • Ndb_conflict_trans_conflict_commit_count : Number of epoch transactions committed after requiring transactional conflict handling. • Ndb_conflict_trans_detect_iter_count : Number of internal iterations required to commit epoch transaction. Should be (slightly) greater than or equal to Ndb_conflict_trans_conflict_commit_count. • Ndb_conflict_trans_reject_count : Number of transactions rejected after being found in conflict by transactional conflict function. 4048