NDB Cluster Configuration Files Default Value OFF Show the mock tables used by  NDB  to support  foreign_key_checks=0 . When this is enabled, extra warnings are shown when creating and dropping the tables. The real (internal) name of the table can be seen in the output of  SHOW CREATE TABLE . • ndb_slave_conflict_role Command-Line Format --ndb-slave-conflict-role=value Deprecated 8.0.23-ndb-8.0.23 System Variable ndb_slave_conflict_role Scope Global Dynamic Yes SET_VAR  Hint Applies No Type Enumeration Default Value NONE Valid Values NONE PRIMARY SECONDARY PASS Deprecated in NDB 8.0.23, and subject to removal in a future release. Use  ndb_conflict_role instead. • ndb_table_no_logging SET @@ndb_table_no_logging = 1; CREATE TABLE A ... ENGINE NDB; CREATE TABLE B ... ENGINE MYISAM; CREATE TABLE C ... ENGINE MYISAM; ALTER TABLE B ENGINE NDB; SET @@ndb_table_no_logging = 0; 4191 When this variable is set to  ON  or  1 , it causes  NDB  tables not to be checkpointed to disk. More specifically, this setting applies to tables which are created or altered using  ENGINE NDB  when ndb_table_no_logging  is enabled, and continues to apply for the lifetime of the table, even if ndb_table_no_logging  is later changed. Suppose that  A ,  B ,  C , and  D  are tables that we create (and perhaps also alter), and that we also change the setting for  ndb_table_no_logging  as shown here: System Variable ndb_table_no_logging Scope Session Dynamic Yes SET_VAR  Hint Applies No Type Boolean Default Value OFF