MySQL 8.0.19 introduces Binlogless replicas with commit ordering which means you can deploy asynchronous replicas without binary logs enabled, and commit transactions in the same order they are replicated in. Yes, you can disable binlog (skip-log-bin) and the logging of changes done by the applier (log-slave-updates=FALSE) while at the same preserve commit order (slave-preserve-commit-order=TRUE).…
Category Archives: High Availability
Automatic Schema Synchronization in NDB Cluster 8.0: Part 2
In part 1, we took a brief, high-level look at the various protocols and mechanisms used to keep the Data Dictionary (DD) of MySQL servers connected to a MySQL Cluster in synchronization with each other and with the NDB Dictionary.…
Faster restarts with local and partial checkpoints in MySQL NDB Cluster
The MySQL NDB Cluster team works on fundamental redesigns of core parts of NDB architecture. One of these changes is the partial checkpoint algorithm. You can now take full advantage of it when building much larger clusters: NDB 8.0 can use 16 TB data memory per data node for in-memory tables.…
Automatic Schema Synchronization in NDB Cluster 8.0: Part 1
Data nodes are the distributed, sharded storage core of MySQL NDB Cluster. Its data is usually accessed by MySQL Servers (also called SQL nodes in NDB parlance). The MySQL servers each have their own transactional Data Dictionary (DD) where all the metadata describing tables, databases, tablespaces, logfile groups, foreign keys, and other objects are stored for use by MySQL server.…
NDB Cluster 8.0 is Generally Available
MySQL’s NDB Cluster Development team proudly announces NDB Cluster 8.0 General Availability.
NDB 8.0.19 GA is a completely new generation of the world’s highest throughput transactional datastore MySQL NDB Cluster. Some of the key highlights of 8.0 are
- NDB is now fully aligned with MySQL Server 8.0
MySQL 8.0.19 Replication Enhancements
Here comes another MySQL release, and together with it, a set of new replication features. As usual, we would like to summarize them. And, also as usual, follow up blogs will provide further details.
- Configure Replication Applier to Require Row-based Replication only.
Automatic member fencing with OFFLINE_MODE in Group Replication
Group Replication enables you to create fault-tolerant systems with redundancy by replicating the system state to a set of servers. Even if some of the servers subsequently fail, as long it is not all or a majority, the system is still available.…
Support for TLS 1.3 in Group Replication
In MySQL 8.0.18, we enhanced the Group Communication System (GCS) layer used by Group Replication (GR) with the ability to use and configure member-to-member connections using TLS v1.3. Therefore, you can secure further your system’s communication with the latest security algorithms.…
Improved handling of different member versions in Group Replication
For optimal compatibility and performance, all members of a group should run the same version of MySQL Server and therefore of Group Replication. However, in some situations, it may be required to that a group contains servers running different versions. For example, during a rolling upgrade.…
Binary Log Encryption: Encryption of Temporary Capture Files
In MySQL 8.0.14 we introduced binary log encryption at rest. When enabled, this feature makes sure that binary log files generated by the server are encrypted as soon as they hit persistent storage.
As of MySQL 8.0.17 transient files created by the server for capturing the changes that end up in the binary log stream are also encrypted.…