MySQL auto-positioning is an integral part of replication with GTID, but it’s neither required nor guaranteed to work. It’s possible to enable GTIDs but disable auto-positioning, and it’s possible that one MySQL instance cannot auto-position on another even when GTIDs are used. The former (GTID on but auto-pos off) is an issue for another time. The latter is the topic of this post: when MySQL GTID auto-positioning fails—and how to fix it.
To avoid infinite replication loops MySQL doesn’t allow
you to have log_slave_updates
and replicate-same-server-id
.
When using GTIDs that may lead to something not expected that you may not be aware of.
In this scenario, we have 2 MySQL servers using GTID. The sever
uuid part of the GTID has been modified in the illustration to
make it more clear. Both servers have
log_slave_updates
enabled too:
So far nothing unusual. So let’s write data on the master (MySQL A):
We can see that this first …
[Read more]Discover the new Continuent Tungsten Replicator (AMI) – the most advanced & flexible replication engine for MySQL, MariaDB & Percona Server, including Amazon RDS MySQL and Amazon Aurora
We’re excited to announce the availability on the Amazon Marketplace of a new version of the Tungsten Replicator (AMI).
Tungsten Replicator (AMI) is a replication engine that provides high-performance and improved replication functionality over the native MySQL replication solution and provides the ability to apply real-time MySQL data feeds into a range of analytics and big data databases.
Tungsten Replicator (AMI) builds upon …
[Read more]This article is an update of a previous post explaining how to setup a second cluster on a second data center to be used as disaster recovery (or to run some off site queries, like long reports, etc..).
This new article covers also the CLONE plugin. Before you ask, CLONE plugin and Replication Channel Based Filters are only available in MySQL 8.0 ! It’s time to upgrade, MySQL 8 is Great !
Also, for DR only, a single MySQL instance acting as asynchronous replica is enough. But if for any reason you want to also have a HA cluster in the second data …
[Read more]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
The latest MySQL 8.0 release is out. That is MySQL 8.0.18. We have some new replication enhancements and some work done on replication internals in this release that we would like to highlight and celebrate with our users. Here is a quick summary.…
Tweet Share
Overview The Skinny
In this blog post, we explore the correct way to implement bi-directional Tungsten Replication between AWS Aurora and Tungsten Clustering for MySQL databases.
Background The Story
When we are approached by a prospect interested in using our solutions, we are proud of our pre-sales process by which that we engage at a very deep technical level to ensure the we provide the best possible solution to meet with the prospect’s requirements. This involves an in-depth hands-on POC, in addition to the significant time and effort we spend building and testing the solution architectures in our lab environment as part of the proposal process.
From time to time, we are presented with requirements that are not always quite so straight forward. Just recently we faced such a situation. A …
[Read more]Mid September, MySQL Community, MySQL Customers and MySQL Engineers will be in San Francisco to share their experience and present the new features of your favorite database !
The event will be held in Moscone South (just Mirko Ortensi‘s Hands-on Lab will be delivered in Moscone West).
During the week, the MySQL Community Team will host the traditional MySQL Reception. We got so great feedback from last year that we decided to renew the experience in the same awesome location, the Samovar Tea Lounge at Yerba Buena Gardens. Don’t forget that you need to register for this reception but no OOW pass is required. Please register here !
Back to the conference, you can find the full schedule for the session in the …
[Read more]
This title may be suitable for the new age MySQL Users. Because
in 5.7 onwards its already supported to enable GTID online. But
still few of my mission critical databases are in 5.6 and
handling 70k QPS
. So I know enabling GTID needs
downtime for this. But in my case, the GTID has been already
implemented. But still the replication is using Binlog file name
and position for replicating the data.
This is my slave status. You can see the GTID has been enabled
but the Auto_Position
is still 0 which means still
my replication is binlog filename and position. No issues with
the replication. But the MySQL world already moved to GTID for
better control on replication and Failover.
Master_Server_Id: 10010
Master_UUID: c924545b-a3e3-11e8-8a39-42010a280410
Master_Info_File: mysql.slave_master_info
SQL_Delay: 0
SQL_Remaining_Delay: NULL …
[Read more]
We are well aware that MySQL Group Replication is one of the faster evolving clustering Technology for MySQL. Flow Control plays a key factor in Group Replication performance and data integrity . In this blog I am going to explain about the Flow Control mechanism and How it has evolved in MySQL 8 ?
What is Flow Control ?
MySQL Group Replication / Native Async replication needs binary logs to get the data flow across the servers.
What makes the difference ?
In the MySQL Group Replication we are trying to achieve the Synchronous replication with the help of a Flow Control mechanism and transaction acknowledgments ( certification ).
Without Flow Control, the MySQL Group Replication is asynchronous replication ? Yes, consistency is lost.
Lets us consider
We have three nodes ( GR1, GR2, GR3 ) . Gr1 is the master and and other two servers ( GR2, GR3 ) are the …
[Read more]