PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-overview-requirements.html
For enhanced reliability, you can use dual switches and dual cards to remove the network as a single point of failure; many device drivers support failover for such communication links. Data node recovery requires synchronization of the failed ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-overview.html
NDB Cluster is designed not to have any single point of failure. NDB Cluster is a technology that enables clustering of in-memory databases in a shared-nothing system. The shared-nothing architecture enables the system to work with very inexpensive ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-privilege-synchronization.html
You should keep in mind that, because shared schema change operations are performed synchronously, the next shared schema change following a change to any shared user or users serves as a synchronization point. NDB 8.0 introduces a new mechanism ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-programs-ndb-restore.html
Rebuilding of unique indexes uses disk write bandwidth for redo logging and local checkpointing. In such cases you can run ndb_restore --rebuild-indexes again; the process resumes at the point where the error occurred. The NDB Cluster restoration ...
https://dev.mysql.com/doc/refman/8.0/en/mysql-cluster-quick.html
To familiarize you with the basics, we describe the simplest possible configuration for a functional NDB Cluster. After this, you should be able to design your desired setup from the information provided in the other relevant sections of 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-conflict-resolution.html
Sets of rows read on the secondary may not necessarily be consistent at a given single point in time. Requirements Source Column Control Conflict Resolution Control Conflict Resolution Functions Conflict Resolution Exceptions Table Conflict ...
https://dev.mysql.com/doc/refman/8.0/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/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-security-mysql-privileges.html
The most important points to remember regarding the MySQL privilege system with regard to NDB Cluster are listed here: Users and privileges established on one SQL node do not automatically exist or take effect on other SQL nodes in the cluster. In ...