Hi all, here is a new post following the blog series on the last MySQLvGroup Replication labs release which already presented: 1) the new features; 2) most asked questions; 3) summary of behaviour and configuration changes; and 4) the performance improvements.…
Group Replication introduces a new way to do replication in MySQL. With great features such as multi-master replication it brings a range of exciting deployment scenarios where some difficult problems become much easier to solve. Group Replication also brings a new set of options that may need to be configured to extract the highest performance from the underlying computing resources.…
The MySQL Utilities Team is pleased to announce a new GA release
of MySQL Utilities. This release includes a number of
improvements for usability, stability, and a few enhancements for
better compatibility with MySQL 5.7. A complete list of all
improvements can be found in our release notes.
This release represents a stable release of the product and is a significant improvement from the 1.5 release. Along with defect patches, we also include the following enhancements.
- Support for MySQL 5.7
- New! Binlog Utilities:
- mysqlbinlogpurge - purge old binary logs
- mysqlbinlogrotate - rotate the binary log
- mysqlbinlogmove - relocate binary log files
- New! Replication Utilities:
Hi everyone, its been a while since the last release of Group
Replication. During this period we have been working hard to
improve the plugin and give you a better user experience. Focused
on solving several existing bugs, address performance issues and
experience we renamed some variables, introduced new ones and changed some of the plugin policies.…
MySQL 5.7.14 was officially released yesterday. So, it's time
to check what bugs reported by MySQL Community in public were
fixed in this release. Some of these bugs are presented
As usual, let me start with InnoDB. The following bugs were fixed there:
- Bug #80296 - "FTS query exceeds result cache limit". It was reported (for 5.6, but I do not see new 5.6 release notes yet) by Monty Solomon and verified by Umesh.
- Bug #80304 - "generated columns don't work with foreign key actions". It was reported by Guilhem Bichot based on test case by Peter Gulutzan presented …
Uber Engineering explains the technical reasoning behind its switch in database technologies, from Postgres to MySQL: https://eng.uber.com/mysql-migration/
These things are always an interesting read, because it looks at one company’s decision making process and operational steps.
At Open Query we’re not a fan of migrations – it doesn’t matter from what brand to what brand, migrations tend to be expensive and painful. Any application tends to be more suited to a particular brand – because of design and implementation choices. This is neither good nor bad, it’s just a fact that has to be acknowledged when considering these things.
Similarly, infrastructure (what hardware there is and how it’s set up and connected) tends to be dependent on the brand choice, as different databases have different needs in that space, …[Read more]
Most people know that you can use SHOW SLAVE STATUS to verify if a slave is running in MySQL. Most people also know that you need to check both Slave_IO_Running and Slave_SQL_Running.
View the code on Gist.
A few years ago, I responded to a question on dba.stackexchange.com on how to verify if a slave is running outside of SHOW SLAVE STATUS.
Prior to MySQL 5.7, you could get this information from SHOW GLOBAL STATUS:
View the code on Gist.
Keep in mind that certain versions of 5.1 …[Read more]
When working with Amazon AWS Aurora, there are some steps to consider when trying to get data out of an active Aurora master into a slave, potentially into a EC2 instance or offsite in another data centre. Creating an external mysql to Aurora gives the option to move out of Aurora, or to have the flexibility to move data around as desired. With AWS RDS instances this task is pretty simple because you can do the following :
- Create a read replica
- Stop the slave process
- Capture the positioning
- Dump the database
With Aurora it’s a little trickier, because a read replica in Aurora has no slave process. All of the replication is handled on the back end and cannot be controlled. However, setting up an external slave can be done.
Amazon AWS Documentation
In …[Read more]
This article discusses how to salvage a
pt-online-schema-change by leveraging
pt-archiver and executing queries to ensure that the
data gets accurately migrated. I will show you how to
continue the data copy process, and how to safely close out the
pt-online-schema-change via manual operations such
RENAME TABLE and
commands. The normal process to recover from a crashed
pt-online-schema-change is to drop the triggers on
your original table and drop the new table created by the script.
Then you would restart
this case, this wasn’t possible.
A customer recently needed to add a primary key column to a very busy table (with around 200 million rows). The table only had a …[Read more]