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.…
Category Archives: High Availability
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.…
A Breakthrough in Usability – Automatic Node Provisioning
As announced in the previous blog post, MySQL InnoDB Cluster just got a very much requested feature which makes a complete, out-of-the-box, easy-to-use and versatile HA solution – Automatic Node Provisioning.
InnoDB cluster users can now rely on it for every single step of cluster deployment and management.…
Automatic provisioning in Group Replication
With the release of version 8.0.17 of MySQL, we bring to you the brand new Clone plugin. Allowing you to get physical snapshots of data stored in InnoDB, this new plugin is an ideal addition to your Group Replication setup.
When joining a new server into a running replication group, a manual offline provisioning procedure was required in most cases as a tool to execute this step in the context of distributed recovery was missing.…
MySQL InnoDB Cluster – Automatic Node Provisioning
The MySQL Development Team is very excited and proud of what was achieved in this 8.0.17 GA release!
The spotlight is on… A game-changer feature – Automatic Node provisioning!
This has been an extremely desired and important feature, and it has been accomplished, once again, with tight integration and cooperation of MySQL Components:
- The new MySQL Clone Plugin: To take a physical snapshot of the database and transfer it over the network to provision a server, all integrated into the server, using regular MySQL connections.
MySQL 8.0.17 Replication Enhancements
MySQL 8.0.17 is out. In addition to fixing a few bugs here and there, we also have a couple of new replication features that I would like to present. Thence, allow me to give you a quick summary. As usual, there shall be follow-up blog posts providing details, so stay tuned.…
No Ping Will Tear Us Apart – Enabling member auto-rejoin in Group Replication
With the release of version 8.0.16 of MySQL, we’ve added some features to the Group Replication (GR) plugin, in order to enhance its high-availability capacities. One of these features was the ability to enable a member that has left the group, under certain circumstances, to automatically rejoin it, without need of intervention by the user.…
Configuring the communication protocol in Group Replication
In a previous blog post we presented the message fragmentation functionality that you can use starting with MySQL Group Replication 8.0.16.
No group member can have a version < 8.0.16 if you wish to use message fragmentation in a group. MySQL 8.0.16 also ships with a new Group Replication concept to help you ensuring backwards compatibility: the group’s communication protocol.…
Enhanced support for large transactions in Group Replication
MySQL 8.0.16 is out and it enhances Group Replication as usual. For example, the group_replication_exit_state_action system variable has a new default value, and members that the group expels can now automatically try to rejoin. This post presents a new feature MySQL 8.0.16 brings to Group Replication: message fragmentation.…
Change group_replication_exit_state_action default option to READ_ONLY
In MySQL 8.0.16, the Group Replication plugin variable group_replication_exit_state_action default value has been changed to READ_ONLY.
The group_replication_exit_state_action plugin variable was introduced in MySQL 8.0.12 to allow the user to configure how Group Replication behaves when a server instance leaves the group unintentionally.
…