Search Results
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-error-handling.html
See also Section 25.2.7.2, “Limits and Differences of NDB Cluster from Standard MySQL Limits”. Starting, stopping, or restarting a node may give rise to temporary errors causing some transactions to fail. When first starting a node, it is ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-exclusive-to-cluster.html
This restriction does not apply to machines simply running mysql or other clients that may be accessing the cluster's SQL nodes. The following are limitations specific to the NDB storage engine: Machine architecture. All machines used in the ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-limitations-unsupported.html
This should not effect NDB Cluster Replication or replication between NDB and other MySQL storage engines. A number of features supported by other storage engines are not supported for NDB tables. Trying to use any of these features in NDB Cluster ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-logs-event-buffer.html
There is one such buffer for each Ndb object subscribing to table events, which means that there are usually two buffers for each mysqld performing binary logging (one buffer for schema events, and one for data events). PARTIALLY_BUFFERING: The ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-diskpagebuffer.html
The diskpagebuffer table provides statistics about disk page buffer usage by NDB Cluster Disk Data tables. The diskpagebuffer table contains the following columns: node_id The data node ID block_instance Block instance pages_written Number of pages ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-membership.html
The membership table describes the view that each data node has of all the others in the cluster, including node group membership, president node, arbitrator, arbitrator successor, arbitrator connection states, and other information. We determine ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-memoryusage.html
Querying this table provides information similar to that provided by the ALL REPORT MemoryUsage command in the ndb_mgm client, or logged by ALL DUMP 1000. The memoryusage table contains the following columns: node_id The node ID of this data node.
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-threads.html
The threads table provides information about threads running in the NDB kernel. You can also set both main and rep to 0, in which case the name of the resulting thread is shown in this table as main_rep_recv, and its description is main, rep and ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-ndbinfo-threadstat.html
The MySQL Server's Event Scheduler can be employed to automate such monitoring. The threadstat table provides a rough snapshot of statistics for threads running in the NDB kernel. The values of the os_ru_utime, os_ru_stime, os_ru_minflt, ...
https://dev.mysql.com/doc/refman/8.4/en/mysql-cluster-programs-ndb-delete-all.html
In some cases, this can be much faster than DELETE or even TRUNCATE TABLE. Usage ndb_delete_all -c connection_string tbl_name -d db_name This deletes all rows from the table named tbl_name in the database named db_name. Options that can be used with ...