PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-mgm-client-commands.html
Using the -i option with RESTART causes the data node to perform an initial restart; that is, the node's file system is deleted and recreated. In addition to the central configuration file, a cluster may also be controlled through a command-line ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cluster-locks.html
This is always one of the values READ, INSERT, UPDATE, DELETE, SCAN, or REFRESH. The cluster_locks table provides information about current lock requests holding and waiting for locks on NDB tables in an NDB Cluster, and is intended as a companion ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cluster-operations.html
(Currently, the MySQL Server does not expose the NDB API transaction ID of an ongoing transaction.) The operation_type column can take any one of the values READ, READ-SH, READ-EX, INSERT, UPDATE, DELETE, WRITE, UNLOCK, REFRESH, SCAN, SCAN-SH, ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-server-locks.html
This is always one of the values READ, INSERT, UPDATE, DELETE, SCAN, or REFRESH. The server_locks table is similar in structure to the cluster_locks table, and provides a subset of the information found in the latter table, but which is specific to ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-server-operations.html
(Currently, the MySQL Server does not expose the NDB API transaction ID of an ongoing transaction.) The operation_type column can take any one of the values READ, READ-SH, READ-EX, INSERT, UPDATE, DELETE, WRITE, UNLOCK, REFRESH, SCAN, SCAN-SH, ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-programs-ndb-desc.html
ndb_desc provides a detailed description of one or more NDB tables. Usage ndb_desc -c connection_string tbl_name -d db_name [options] ndb_desc -c connection_string index_name -d db_name -t tbl_name Additional options that can be used with ndb_desc ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-replication-pitr.html
Point-in-time recovery—that is, recovery of data changes made since a given point in time—is performed after restoring a full backup that returns the server to its state when the backup was made. Performing point-in-time recovery of NDB Cluster ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-rolling-restart.html
To free memory previously allocated to a table by successive INSERT and DELETE operations, for re-use by other NDB Cluster tables. This section discusses how to perform a rolling restart of an NDB Cluster installation, so called because it involves ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-sql-statements.html
This section discusses several SQL statements that can prove useful in managing and monitoring a MySQL server that is connected to an NDB Cluster, and in some cases provide information about the cluster itself. SHOW ENGINE NDB STATUS, SHOW ENGINE ...
https://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-upgrade-downgrade-7-5.html
A workaround for an upgrade that has failed for these reasons can be accomplished as follows: Perform a rolling restart of the entire cluster Delete all .frm files in the data/ndbinfo directory Run mysql_upgrade. This section provides information ...