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.…
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.…
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.…
In MySQL 8.0.16, the Group Replication plugin variable group_replication_exit_state_action default value has been changed to READ_ONLY.
Starting on version 8.0.16, MySQL server introduces a new command that allows
for the binary log master key rotation, online!
When binary log encryption is enabled, the binary log master key can be rotated online by using the following new command:
ALTER INSTANCE ROTATE BINLOG MASTER KEY;
This new command can be used to rotate the binary log master key periodically or whenever you suspect that a key might have been compromised.…
MySQL 8.0.16 has been released last Thursday. In it, you can find some new replication features. Here is a quick summary. Follow-up blog posts will provide details about these features.
- Large Messages Fragmentation Layer for Group Replication. Tiago Vale’s work, introduces message fragmentation to the Group Communication Framework.
On previous posts about Group Replication consistency we:
- introduced consistency levels;
- explained how to configure the primary failover consistency;
- presented how to configure transaction consistency levels to achieve the consistency required by your applications.
In blog 3. we presented the consistency levels: EVENTUAL, BEFORE, AFTER and BEFORE_AND_AFTER; their scopes: SESSION, GLOBAL; and their context: whether they only impact the ongoing transaction or all concurrent transactions.…
In 8.0.14, we add to Group Replication (GR) the ability to use IPv6 in all of its network-related configuration parameters. This means that now you can take advantage of this technology and “rock” those billion addresses using MySQL Group Replication.
When you operate a Group Replication group, some variables use network addresses, mainly:
In Group Replication, starting with MySQL 8.0.12, the user is able to specify the behavior for members that enter an error state. The member can either shoot itself on the head or set itself to read-only.
But what does that mean in practice?…
As you may have noticed by now, we are continuously improving and enhancing the experience of managing a MySQL server. Furthermore, we have also released tools, such as MySQL shell, that make advanced and distributed setups like creating, deploying, and running clusters of InnoDB instances, seamless to the end user.…