Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-syntax.html
In such cases, statistical information is not generated, which means a nonoptimal execution plan may be selected. The other partitioning extensions to ALTER TABLE—ADD PARTITION, REORGANIZE PARTITION, and COALESCE PARTITION—are supported for NDB ... Some SQL statements relating to certain MySQL features produce errors when used with NDB tables, as described in the following list: Temporary ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndb-api-statistics.html
NDB API applications can read the values of the counters for use in optimization or monitoring. A number of types of statistical counters relating to actions performed by or affecting Ndb objects are available. Such actions include starting and ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndb-innodb-engines.html
The NDB storage engine is implemented using a distributed, shared-nothing architecture, which causes it to behave differently from InnoDB in a number of ways. For those unaccustomed to working with NDB, unexpected behaviors can arise due to its ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbd-definition.html
SpinMethod Version (or later) NDB 8.4.0 Type or units enumeration Default StaticSpinning Range CostBasedSpinning, LatencyOptimisedSpinning, DatabaseMachineSpinning, StaticSpinning Restart Type Node Restart: Requires a rolling restart of the cluster.
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-memory-per-fragment.html
OPTIMIZE TABLE can be used to defragment a table's variable-sized pages; this moves row variable-sized parts between pages so that some whole pages can be freed for re-use. memory_per_fragment Table: Notes memory_per_fragment Table: Examples The ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-online-operations.html
This does not perform any defragmentation, which requires an OPTIMIZE TABLE or null ALTER TABLE statement. MySQL NDB Cluster supports online table schema changes using ALTER TABLE ... NDB Cluster handles COPY and INPLACE as described in the next ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-params-ndbd.html
SchedulerResponsiveness: Set NDB scheduler response optimization 0-10; higher values provide better response time but lower throughput. The listings in this section provide information about parameters used in the [ndbd] or [ndbd default] sections ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-conflict-resolution.html
Due to the fact that no timestamp is available for a delete operation, a delete using NDB$MAX() is in fact processed as NDB$OLD, but for some use cases, this is not optimal. Requirements Source Column Control Conflict Resolution Control Conflict ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-replication-schema.html
Important For insert conflict resolution using NDB$MAX_INS() or NDB$MAX_DEL_WIN_INS(), an SQL node (that is, a mysqld process) can record row updates on the source cluster as WRITE_ROW events with the --ndb-log-update-as-write option enabled for ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-command-options.html
Note The mysql client always passes optimizer hints to the server, regardless of whether this option is given. mysql supports the following options, which can be specified on the command line or in the [mysql] and [client] groups of an option file.