There is a new MySQL 8.0 release and it has some interesting replication features. The change log is available at the usual place, MySQL 8.0.21, but let me give you a brief summary.
- Binary Log Checksums Support for Group Replication (WL#9038).
MySQL Terminology Updates
It’s been 20 years since MySQL Replication was introduced in MySQL 3.23.15 (Released in May 2000). Since then, virtually every MySQL Database deployment in production has been using Replication in order to achieve high availability, disaster recovery, read scale out and various other purposes.…
Enforce Primary Key constraints on Replication
In this post, we introduce a configuration option that controls whether replication channels allow the creation of tables without primary keys. This continues our recent work on replication security, where we allowed users to enforce privilege checks, and/or enforce row-based events.…
MySQL 8.0.20 Replication Enhancements
We have just released MySQL 8.0.20. And it has some interesting replication enhancements. In particular one big and exciting feature: binary log compression. Here is the list of things in this release:
- Binary Log Compression (WL#3549). This work done by Luís Soares implements binary log compression, making use of the popular compression algorithm ZSTD.
MySQL User Camp, Bangalore, India – 5th March 2020
A MySQL User Camp was held on 5th March 2020 at Oracle India Pvt Ltd, Kalyani Magnum Infotech Park, Bangalore, India. The attendees included developers, DBAs and trainers from Amex, Robert Bosch, Flipkart and others.
Sanjay Manwani, the Senior Director of MySQL Engineering India, presented an informative session which highlighted MySQL’s recent achievements like the DB of the Year award and the #1 ranking in the Most Popular DB with Developers StackOverflow survey.…
Preserving commit order on replicas with binary log disabled
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).…
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