PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/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/8.0/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/8.0/en/mysql-cluster-ndbinfo-server-locks.html
This information can be used to help identify the unique entries in a list of lock requests. The lock ID (lockid column) is unique to this node and block instance. The server_locks table is similar in structure to the cluster_locks table, and ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-tc-time-track-stats.html
Each TC instance tracks latencies for a set of activities it undertakes on behalf of API nodes or other data nodes; these activities include transactions, transaction errors, key reads, key writes, unique index operations, failed key operations of ... 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 ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-size-pl.html
Memory requirements for all of the tables, attributes, ordered indexes, and unique hash indexes defined in the database. This is a Perl script that can be used to estimate the amount of space that would be required by a MySQL database if it were ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-general.html
Each MySQL server used for replication in either cluster must be uniquely identified among all the MySQL replication servers participating in either cluster (you cannot have replication servers on both the source and replica clusters sharing the ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-preparation.html
Ensure that each MySQL server acting as a replication source is assigned a unique server ID, and has binary logging enabled, using the row-based format. Preparing the NDB Cluster for replication consists of the following steps: Check all MySQL ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-starting.html
Start the MySQL replication source server by issuing this command, where id is this server's unique ID (see Section 25.7.2, “General Requirements for NDB Cluster Replication”): shellS> mysqld --ndbcluster --server-id=id \ --log-bin --ndb-log-bin ... This section outlines the procedure for starting NDB Cluster replication using a single replication ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-shm-definition.html
(NDB 8.0.13) To retrace the path of a distributed message, it is necessary to provide each message with a unique identifier. (NDB 8.0.13) When setting up shared memory segments, a node ID, expressed as an integer, is used to identify uniquely the ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-tcp-definition.html
These are the same unique Id values for each of these nodes as described in Section 25.4.3.7, “Defining SQL and Other API Nodes in an NDB Cluster”. These are the same unique Id values for each of these nodes as described in Section 25.4.3.7, ...