NDB Cluster Configuration Files Maximum Value 1200 Unit seconds Command-Line Format --ndb-distribution={KEYHASH|LINHASH} System Variable ndb_distribution Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Enumeration Default Value KEYHASH Valid Values LINHASH KEYHASH Command-Line Format --ndb-log-apply-status[={OFF|ON}] System Variable ndb_log_apply_status Scope Global Dynamic No SET_VAR  Hint Applies No Type Boolean Default Value OFF 4166 This option has no effect unless the MySQL server is started with the  --ndbcluster  option. In a circular replication setup, this option causes changes to  ndb_apply_status  tables to complete the entire circuit, eventually propagating back to the originating NDB Cluster. This also allows a cluster acting as a replication source to see when its changes (epochs) have been applied to the other clusters in the circle. In a chain replication setup, using this option allows downstream (replica) clusters to be aware of their positions relative to all of their upstream contributors (sourcess). Causes a replica  mysqld  to log any updates received from its immediate source to the mysql.ndb_apply_status  table in its own binary log using its own server ID rather than the server ID of the source. In a circular or chain replication setting, this allows such updates to propagate to the  mysql.ndb_apply_status  tables of any MySQL servers configured as replicas of the current mysqld . Controls the default distribution method for  NDB  tables. Can be set to either of  KEYHASH  (key hashing) or LINHASH  (linear hashing).  KEYHASH  is the default. Specifies the maximum time in seconds that this  mysqld  waits for a schema operation to complete before marking it as having timed out. • --ndb-distribution=[KEYHASH|LINHASH] • --ndb-log-apply-status