Starting on MySQL 8.0.1, a very updated replica server will be more efficient (and probably faster) than previous MySQL versions because of improvements in the relationship between the replication threads. Preliminary testing showed a benefit of up to 65% on Sysbench Update Index.…
10 Older Entries »
The new release of MySQL is packed with exciting features that help detecting and analyzing replication lag. In this post, you will be able to learn all about the new replication timestamps, the new useful information that is now reported by performance schema tables, and how delayed replication was improved.…
On the same day last year, I wrote a post about replication filters in MySQL Multi Source Replication and whether we can set the filters per replication channel or not (Bug #80843). My feature request – as well as some others – has been implemented in MySQL 8.0.1. Thanks Oracle for the implementation. (Full list of changes can be checked out here)
In this post, I’ll demonstrate how to set replication filters per
channel in MySQL Multi Source Replication.
Setting up and configuring Multi Source …[Read more]
This blog we describe an issue with MySQL 5.7’s super_read_only feature when used alongside with GTID in chained slave instances.
In MySQL 5.7.5 and onward introduced the
gtid_executed table in the MySQL database to store
every GTID. This allows slave instances to use the GTID feature
regardless whether the binlog option is set or not. Here is an
example of the rows in the
mysql> SELECT * FROM mysql.gtid_executed; +--------------------------------------+----------------+--------------+ | source_uuid | interval_start | interval_end | …[Read more]
Great news: Group Replication is now officially released with MySQL 5.7.17, congratulations to everybody that worked so hard for it!
In this post I plan to share more details about the performance of Group Replication while addressing one of our frequently asked questions, which is how it performs compared to Galera.…
Multi-Source Replication is one of the awesome
features in MySQL 5.7 which allows the slave to get the
replication streams from multiple masters by having a replication
channel for each master.
But what about the replication filters? Can we set replication filters per channel in the multi-source replication?
In brief, replication filtering is a way used to eliminate part
of the master’s events (not) to be replicated to the slaves (Also
known as Partial Replication). This can be done on either master
--binlog-ignore-db options) or slaves (using
--replicate-* options) while it is not recommended
on the master anyway at least to provide Point in Time Recovery
In the first post, I showed you how to use the
tools in a typical MySQL replication setup. In this post, we’ll discuss MySQL replication for more advanced topologies. I will show you how to use these tools in a chained …[Read more]
When using a multi-threaded slave, the
STOP SLAVE command could take a long
time to return because the slave waited for workers to catch up
processing the queue. This blog post is about improvements that
have been made in MySQL 5.6.26 and later to ensure that
STOP SLAVE returns quickly when using
a multi-threaded slave (MTS).…
MySQL’s multi-source replication allows you to replicate data from multiple databases into one database in parallel (at the same time). This post will explain and show you how to set up multi-source replication. (WARNING: This is a very long and detailed post. You might want to grab a sandwich and a drink.)
In most replication environments, you have one master database and one or more slave databases. This topology is used for high-availability scenarios, where the reads and writes are split between multiple servers. Your application sends the writes to the master, and reads data from the slaves. This is one way to scale MySQL horizontally for reads, as you can have more than one slave. Multi-source replication allows you to write to multiple MySQL instances, and then combine the data into one server.
Here is a quick overview of …[Read more]
MySQL 5.7 has been recently declared Generally Available and in it there is a set of new replication features. Over the last 6 years MySQL replication has evolved at a tremendous pace. MySQL 5.6 brought us a lot of new replication features, many that were ground breaking and yes, sometimes controversial.…
10 Older Entries »