PDF (US Ltr)
- 43.2Mb
PDF (A4)
- 43.3Mb
Man Pages (TGZ)
- 295.2Kb
Man Pages (Zip)
- 400.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-config-starting.html
Changes in configuration are also likely to be indicated when changes are made in the platform on which the cluster is run, or in applications that use the NDB Cluster 's data. For these reasons, it is not possible to offer a single configuration ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-log-startup-messages.html
Possible startup messages with descriptions are provided in the following list: Initial start, waiting for %s to connect, nodes [ all: %s connected: %s no-wait: %s ] Waiting until nodes: %s connects, nodes [ all: %s connected: %s no-wait: %s ] ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-ndbinfo-transporter-details.html
This table contains information about individual NDB transporters, rather than aggregate information as shown by the transporters table. sendbuffer_used_bytes The amount, in bytes, of signal data currently awaiting send by this transporter.
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-online-add-node-example.html
In this section we provide a detailed example illustrating how to add new NDB Cluster data nodes online, starting with an NDB Cluster having 2 data nodes in a single node group and concluding with a cluster having 4 data nodes in 2 node groups.
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-issues.html
This section discusses known problems or issues when using replication with NDB Cluster. A loss of connection can occur either between the source cluster SQL node and the replica cluster SQL node, or between the source SQL node and the data nodes ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-start-phases.html
This section provides a simplified outline of the steps involved when NDB Cluster data nodes are started. More complete information can be found in NDB Cluster Start Phases, in the NDB Internals Guide. These phases are the same as those reported in ...
https://dev.mysql.com/doc/refman/8.0/en/mysqlbinlog-server-id.html
When invoked with the --read-from-remote-server option, mysqlbinlog connects to a MySQL server, specifies a server ID to identify itself, and requests binary log files from the server. You can use mysqlbinlog to request log files from a server in ...
https://dev.mysql.com/doc/refman/8.0/en/performance-schema-replication-tables.html
This is similar to the information available from the SHOW REPLICA STATUS statement, but representation in table form is more accessible and has usability benefits: SHOW REPLICA STATUS output is useful for visual inspection, but not so much for ...
https://dev.mysql.com/doc/refman/8.0/en/query-log.html
The general query log is a general record of what mysqld is doing. The server writes information to this log when clients connect or disconnect, and it logs each SQL statement received from clients. The general query log can be very useful when you ...