PDF (US Ltr)
- 41.9Mb
PDF (A4)
- 42.0Mb
Man Pages (TGZ)
- 272.3Kb
Man Pages (Zip)
- 378.3Kb
Info (Gzip)
- 4.2Mb
Info (Zip)
- 4.2Mb
Search Results
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-ndbinfo-blobs.html
Parts of JSON values exceeding 4000 bytes in size are also stored in this table. For more information about how NDB Cluster stores columns of such types, see String Type Storage Requirements. The part and inline sizes of NDB blob columns can be set ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-ndbinfo-cluster-locks.html
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 table to cluster_operations. Information obtain from the cluster_locks table may ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-ndbinfo-dict-obj-info.html
The dict_obj_info table provides information about NDB data dictionary (DICT) objects such as tables and indexes. (The dict_obj_types table can be queried for a list of all the types.) This information includes the object's type, state, parent ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-ndbinfo-index-columns.html
This table provides information about indexes on NDB tables. The columns of the index_columns table are listed here, along with brief descriptions: table_id Unique ID of the NDB table for which the index is defined Name of the database containing ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-ndbinfo-server-locks.html
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 the SQL node (MySQL server) where it resides. (The cluster_locks table provides ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-ndbinfo-tc-time-track-stats.html
The tc_time_track_stats table provides time-tracking information obtained from the DBTC block (TC) instances in the data nodes, through API nodes access NDB. Each TC instance tracks latencies for a set of activities it undertakes on behalf of API ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-replication-general.html
A replication channel requires two MySQL servers acting as replication servers (one each for the source and replica). For example, this means that in the case of a replication setup with two replication channels (to provide an extra channel for ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-replication-preparation.html
Preparing the NDB Cluster for replication consists of the following steps: Check all MySQL servers for version compatibility (see Section 25.7.2, “General Requirements for NDB Cluster Replication”). To provide replication backup capability, you ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-replication-starting.html
This section outlines the procedure for starting NDB Cluster replication using a single replication channel. Start the MySQL replication source server by issuing this command, where id is this server's unique ID (see Section 25.7.2, “General ...
https://dev.mysql.com/doc/refman/9.7/en/mysql-cluster-shm-definition.html
Communications between NDB cluster nodes are normally handled using TCP/IP. The shared memory (SHM) transporter is distinguished by the fact that signals are transmitted by writing in memory rather than on a socket. The shared-memory transporter ...