MySQL InnoDB Cluster – Real-World Cluster Tutorial for OEL, Fedora, RHEL and CentOS

In this tutorial, we are going to guide you through the process of preparing and configuring RPM based distributions, such as OEL, Fedora or CentOS, for InnoDB cluster usage. We will address the steps from the initial configurations, to the cluster creation, and finally the MySQL Router configuration to map the data traffic.…

MySQL InnoDB Cluster – What’s New in the Release Candidate

We carefully listened to the feedback we got from the last preview release and incorporated many of the suggested changes. On top of that, we have fixed several bugs and extended existing functionalities.

Here are the highlights of this release!

MySQL Shell / X AdminAPI

We keep aiming at the goal of hiding the complexity associated with configuring and managing H/A setups, but on top of that, we see usability as a great priority.…

Upgrading your MySQL Server Farm

There are several advantages to keeping up to date with the latest major versions of MySQL. To provide a short example using MySQL 5.7:

  • Let application developers benefit from new functionality, e.g. JSON in 5.7
  • Use your hardware infrastructure more efficiently with parallel slaves in 5.7
  • Improve monitoring or management for DevOps with more performance schema instrumentation in 5.7
  • Improve security by using features like  transparent data encryption, firewall, auditing, and sha256 authentication in 5.7
  • Keep within the EOL window for access to maintenance releases and support

This blog post explains general activities in an upgrade project and what to look out for prior to an upgrade between major MySQL Server releases.…

Sushi = Beer ?! An introduction of UTF8 support in MySQL 8.0

In MySQL 8.0 our plan is to drastically improve support for utf8. While utf8 support itself dates back to MySQL 4.1, there exist some limitations. The “sushi = beer” problem in the title refers to Bug #76553. Sushi and beer don’t even go well together, at least not to my taste:-) I will use this bug as an example to explain issues with utf8 collations in the past and our plans for utf8 support going forward.…