MySQL 8.0.1 has just been released with a wonderful set of features across the board. Specifically in replication, there is plenty of new and exciting functionality as well as performance improvements. In this post I am going to summarize the replication features of this development milestone release.…
I had not reviewed MySQL 5.7 release notes for quite a some time
in this series. Last time I checked it was MySQL 5.7.15. So, as soon as I noted new
release, 5.7.18, I decided to check the release notes
for any interesting fixed bug (reported by Community users in
public) in the areas I am interested in: InnoDB, replication,
optimizer and few others.
Note that recently most of the bugs fixed are internal only, found by Oracle engineers that never cared (or are not allowed, who knows) to report them in public, so this blog post is not even remotely a full review of what's fixed in MySQL 5.7.18 and is not a replacement for reading the detailed …
I read with interest MySQL High Availability tools - Comparing MHA, MRM and ClusterControl by SeveralNines. I thought there was a missing piece in the comparison: orchestrator, and that as result the comparion was missing scope and context.
I'd like to add my thoughts on topics addressed in the post. I'm
by no means an expert on MHA, MRM or ClusterControl, and will
mostly focus on how
orchestrator tackles high
availability issues raised in the post.
What this is
This is to add insights on the complexity of failovers. Over the duration of three years, I always think I've seen it all, and then get hit by yet a new crazy scenario. Doing the right thing automatically is difficult.
In this post, I'm …[Read more]
Back in January 2014, some time after many nice people
kindly asked me to shut up stop writing about MySQL bugs on
Facebook several times per day, I decided to start reading
the fine MySQL Manual more carefully than before and report
not only typos there, but also any topic or detail not properly
explained. Usually these reports, tagged as "missing manual", were the result of careful
study of the documentation based on real user question or
customer issue. So, most of these reports came from real life,
and missing information badly affected poor MySQL users.
Today, for this issue #50 in my series of posts about MySQL bugs, I decided to list and …
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.…
In this tutorial, we are going to guide you through the whole process of configuring Debian based distributions for InnoDB cluster usage; the most popular being Ubuntu. We will address the steps from the initial configurations, to the cluster creation, and finally the MySQL Router configuration to map the data traffic.…
Nowadays, it’s very important to have a high availability solution that gives you serenity and security for your data. The task of ensuring your data will always be available is a challenging one, that not everyone wants to do because it demands a lot of knowledge about tools, configuration, and technologies.…
MySQL Cluster is a highly available, distributed, shared-nothing database with very interesting performance characteristics for some workloads. Among other features, it supports automatic sharding and allows us to bypass the SQL layer if we don’t need it, via the NDB API (which in my eyes, makes it one of the few transactional nosql databases out there).
In this post, I’ll describe how we can set up replication from MySQL Cluster into a standalone MySQL server using Innodb as the storage engine.
There are a few reasons to set up replication between MySQL Cluster and a non-NDB based MySQL server. These reasons include (but are not limited to): the need …[Read more]
Quick post today, because I wanted to share a snippet (actually,
a patch) that allows the great xtrabackup tool to take backups of MariaDB when
multi source replication is in use.
Granted, this is supported already, except the slave(s) position is not saved when the backup is taken, and this somewhat defeats the purpose of the backup, which should be used to rebuild the server and resync it with its master(s) in case of disaster.
A workaround for using xtrabackup with MariaDB exists, but only works when you have a single master: just set the default_master_connection variable in your my.cnf to the name of your master connection, and you are set - in fact, in this situation, SHOW SLAVE STATUS will work exactly the same as in stock MySQL, and xtrabackup is happy.
The trouble begins when you have …