MySQL 8.0.0 was released today. It has been some time in the making, shrouded in a veil of secrecy for over one year. We knew, from listening to the gossip and looking at the few available previews, some of what was going to bring. So, for the observant users, its main features may not come as a surprise. For the rest of you, here's a quick roundup:

Notable features

• No MyISAM tables anymore! The grant tables are now InnoDB, meaning that grant operations are now atomic.
• A real data dictionary. This change is less visible than the previous one. The data dictionary tables are hidden and only a subset of the data is available through information_schema views. The reason for the hidden tables is to allow a stable interface through several versions. I am …

In this blog, I will provide answers to the Q & A for the MySQL Replication Troubleshooting webinar.

First, I want to thank everybody for attending the August 25 webinar. The recording and slides for the webinar are available here. Below is the list of your questions that I wasn’t able to answer during the webinar, with responses:

Q: Hi Sveta. One question: how is it possible to get N previous events using the SHOW BINLOG EVENTS command? For example, the position is 999 and I want to analyze the previous five events. Is it possible?

A: Not, there is no such option. You cannot get the previous five events using

SHOW BINLOG EVENTS

. …

Some time ago, feedback was requested on new replication default after MySQL 5.7.  Some of the suggested default are:

relay-log-info-repository = TABLE (previous default FILE) relay-log-recovery = ON (previous default OFF) master-info-repository = TABLE (previous default FILE) sync-master-info = 1,000 (previous default 10,000) sync-relay-log = 1,000 (previous default 10,000)

I agree on the

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.

Many Improvements!
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 improving user
experience we renamed some variables, introduced new ones and changed some of the plugin policies.…

Hi everyone! It has been some time since the last MySQL Group Replication labs release was out. But the team has not been sitting on its hands. As such, it is time for a new labs release with new features, bug fixes and improvements across the board.…

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 …

Overview

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 :

1. Create a read replica
2. Stop the slave process
3. Capture the positioning
4. 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 …