PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.5Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-drop-table.html
Usage ndb_drop_table -c connection_string tbl_name -d db_name Options that can be used with ndb_drop_table are shown in the following table. --connect-retries Command-Line Format --connect-retries=# Type Integer Default Value 12 Minimum Value 0 ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-mgmd.html
The files are named sequentially in order of creation using the following format: ndb_node-id_config.bin.seq-number node-id is the management server's node ID; seq-number is a sequence number, beginning with 1. The management server is the process ...
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 ...
25.7.9.1 NDB Cluster Replication: Automating Synchronization of the Replica to the Source Binary Log
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-auto-sync.html
It is possible to automate much of the process described in the previous section (see Section 25.7.9, “NDB Cluster Backups With NDB Cluster Replication”). The following Perl script reset-replica.pl serves as an example of how you can do this.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication-backups.html
This section discusses making backups and restoring from them using NDB Cluster replication. We assume that the replication servers have already been configured as covered previously (see Section 25.7.5, “Preparing the NDB Cluster for ...
https://dev.mysql.com/doc/refman/8.0/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/8.0/en/mysql-cluster-replication-two-channels.html
In a more complete example scenario, we envision two replication channels to provide redundancy and thereby guard against possible failure of a single replication channel. This requires a total of four replication servers, two source servers on the ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-replication.html
This thread ensures that all changes in the cluster producing the binary log—and not just those changes that are effected through the MySQL Server—are inserted into the binary log with the correct serialization order. NDB Cluster supports ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-enterprise-telemetry.html
It enables users to instrument their applications in order to export observability data: traces, metrics and logs, enabling increased granularity of debugging and testing. The MySQL telemetry component is based on the OpenTelemetry (OTel) project, ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-installer-catalog-dashboard.html
When the Automatic option is selected, MySQL Installer attempts to connect to each default URL in the list (in order) until a connection is made. This section describes the MySQL Installer product catalog, the dashboard, and other actions related ...