https://dev.mysql.com/mysql-cluster-ndbinfo-counters.html
ATTRINFO keeps a count of the number of times an interpreted program is sent to the data node. The counters table provides running totals of events such as reads and writes for specific kernel blocks and data nodes. Counts are kept from the most ...
https://dev.mysql.com/mysql-cluster-ndbinfo-server-transactions.html
The server_transactions table is subset of the cluster_transactions table, but includes only those transactions in which the current SQL node (MySQL Server) is a participant, while including the relevant connection IDs. The following table provides ...
https://dev.mysql.com/mysql-cluster-online-add-node-basics.html
Note This needs to be done only for tables already existing at the time the new node group is added. In this section, we list the basic steps required to add new data nodes to an NDB Cluster. This procedure applies whether you are using ndbd or ...
https://dev.mysql.com/mysql-cluster-params-mgmd.html
HeartbeatIntervalMgmdMgmd: Time between management-node-to-management-node heartbeats; connection between management nodes is considered lost after 3 missed heartbeats. The listing in this section provides information about parameters used in the ...
https://dev.mysql.com/mysql-cluster-programs-ndb-waiter.html
ndb_waiter repeatedly (each 100 milliseconds) prints out the status of all cluster data nodes until either the cluster reaches a given status or the --timeout limit is exceeded, then exits. By default, it waits for the cluster to achieve STARTED ...
https://dev.mysql.com/mysql-cluster-replication-failover.html
In the event that the primary Cluster replication process fails, it is possible to switch over to the secondary replication channel. This means that the ndb_apply_status table contains information for the slave on this host as well as for any other ...
https://dev.mysql.com/mysql-cluster-replication-issues.html
This section discusses known problems or issues when using replication with NDB Cluster 8.0. A loss of connection can occur either between the replication master SQL node and the replication slave SQL node, or between the replication master SQL ...
https://dev.mysql.com/mysql-cluster-replication-multi-master.html
It is possible to use NDB Cluster in multi-master replication, including circular replication between a number of NDB Clusters. Each cluster has two SQL nodes, with SQL nodes A and B belonging to Cluster 1, SQL nodes C and D belonging to Cluster 2, ...
https://dev.mysql.com/mysql-cluster-replication-preparation.html
If the master cluster is already in use, you can create a backup of the master and load this onto the slave to cut down on the amount of time required for the slave to synchronize itself with the master. Preparing the NDB Cluster for replication ...
https://dev.mysql.com/mysql-cluster-security-mysql-security-procedures.html
Without FLUSH PRIVILEGES, the changes do not take effect until the next time that the server is restarted. In this section, we discuss MySQL standard security procedures as they apply to running NDB Cluster. In general, any standard procedure for ...