Since MySQL 8.0.22 there is a mechanism in asynchronous replication that makes the receiver automatically try to re-establish an asynchronous replication connection to another sender, in case the current connection gets interrupted due to the failure of the current sender.
The post Automatic connection failover for Asynchronous Replication first appeared on dasini.net - Diary of a MySQL expert.
ProxySQL is proud to announce the latest release of ProxySQL version 2.0.15 on the 30th of October 2020
ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.
Release Overview Highlights
ProxySQL v2.0.15 is a patch release comprising of minor backward compatible changes and bug fixes.
The most interesting highlight of this release is the introduction of ARMv8 64-bit packages which have been compiled for CentOS-RHEL 7/8, Debian 9/10 and Ubuntu 18/20 as well as a Docker image available on our …
[Read more]MySQL 8.0.22 was released roughly a week ago. It includes some nice additions to replication that we would like to call out. Here they are:
… Tweet Share
MySQL NDB Cluster 8.0.22 is available to download now!
8.0.22 brings a lot of exciting new features and improvements like all our quarterly updates to 8.0.
IPv6 is now supported between all cluster nodes types. It works in dual stack environments and IPv6-only environments.…
Tweet Share
For what reason should I use a real multi-primary setup?
To be clear, not a multi-writer solution where any node can become the active writer in case of needs, as for Percona XtraDB Cluster (PXC) or Percona Server for MySQL using Group_replication. No, we are talking about a multi-primary setup where I can write at the same time on multiple nodes. I want to insist on this “why?”.
After having excluded the possible solutions mentioned above, both covering the famous 99.995% availability, which is 26.30 minutes of downtime in a year, what is left?
Disaster Recovery? Well, that is something I would love to have, but to be a real DR solution we need to put several kilometers (miles for imperial) in the middle.
And we know …
[Read more]ProxySQL is proud to announce the release of the latest stable version of ProxySQL 2.0.14 on the 8th of September 2020
ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.
Release Overview Highlights
Before discussing the features and fixes in this release we’d like to mention that we are aware of the delays in new releases. Ideally we would like to release ProxySQL more rapidly however we have recently been focusing our development efforts on ProxySQL 2.1.
The next edition of ProxySQL brings improved performance as well as many new and exciting …
[Read more]As Group Replication (GR) matures and it is deployed in a myriad of different systems, we begin to witness specific network conditions that we must be able to cope with in order to make Group Replication more tolerant and robust to those failures.…
Tweet Share
From MySQL 8.0.21 onwards, START GROUP_REPLICATION
includes new options which allow a user to specify credentials to
be used for distributed recovery. You can now pass credentials
when invoking START GROUP_REPLICATION instead of
setting them when configuring the
group_replication_recovery channel.
START GROUP_REPLICATION command now has the options:
USER: User name.
… Tweet Share
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.…
Tweet Share
Group Replication distributed recovery is one of the key features and until now it was restricted to be executed over one mysql connection point automatically defined on mysql system variables port and host.
With group_replication_recovery_endpoints we
can specify through which interfaces can group replication
recovery take place for a given member so that it controls where
recovery traffic flows in the network infrastructure.…
Tweet Share