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-api-definition.html
The [mysqld] and [api] sections in the config.ini file define the behavior of the MySQL servers (SQL nodes) and other applications (API nodes) used to access cluster data. If no computer or host name is provided, any host can use this SQL or API ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-importing-data.html
This data is most often available in one or more of the following formats: An SQL dump file such as produced by mysqldump or mysqlpump. Within a mysql client session, you can perform the import using the following SQL statements: SET ... It is ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-logs-cluster-log.html
The following table lists the most common NDB cluster log messages. For information about the cluster log, log events, and event types, see Section 25.6.3, “Event Reports Generated in NDB Cluster”. These log messages also correspond to log ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/mysql-cluster-options-variables.html
This is generally not recommended, although it may be useful to disable transaction support within a given client session when that session is used to import one or more dump files with large transactions; this allows a multi-row insert to be ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-restore.html
--tab=dir_name, -T dir_name Command-Line Format --tab=path Type Directory name Causes --print-data to create dump files, one per table, each named tbl_name.txt. The NDB Cluster restoration program is implemented as a separate command-line utility ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-pitr.html
Performing point-in-time recovery of NDB Cluster tables with NDB Cluster and NDB Cluster Replication can be accomplished using a native NDB data backup (taken by issuing CREATE BACKUP in the ndb_mgm client) and restoring the ndb_binlog_index table ... 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 ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-rolling-restart.html
Use mysqldump to create a backup prior to the upgrade; afterward, restore the dump using LOAD DATA. This section discusses how to perform a rolling restart of an NDB Cluster installation, so called because it involves stopping and starting (or ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-commands.html
If there is a concern that optimizer-hint comments may be stored in object definitions so that dump files when reloaded with mysql would result in execution of such commands, either invoke mysql with the --binary-mode option or use a reload client ... mysql sends each SQL statement that you issue to the server to be ...
https://dev.mysql.com/doc/refman/8.0/en/no-matching-rows.html
You can create a test file by dumping the tables with mysqldump --quick db_name tbl_name_1 ... If you have a complicated query that uses many tables but that returns no rows, you should use the following procedure to find out what is wrong: Test ...