Great news! MySQL 8.0.3 is out and it is a release candidate. In the replication team we have been busy working on interesting new enhancements and also doing some clean up. Some of these new features are out in this release.…
10 Older Entries »
Comparing Oracle MySQL Group Replication and Galera Cluster through a probability perpective seems quite interesting.
At commit time both use a group certification process that requires network round trips. The required time for these network roundtrips is what will mainly determined the cost of a transaction. Let us try to compute an estimate of the [...]
In development milestone release (DMR) version 8.0.2 we are changing several replication options. The motivation behind this is simply that we want our users to enjoy default installations with the best efficient setup, configuration and performance. We also don’t want users to struggle getting them to work optimally.…
This week is special and full of anniversaries for me. This week
5 years ago I left Oracle behind and joined Percona... Same week
5 years ago I had written something about MySQL in this blog for the
first time in my life. 5 years ago I've created my Facebook account that I actively (ab)use for discussing work-related issues.
So, to summarize, it's a five years anniversary of my coming out
as a MySQL Entomologist, somebody who writes and speaks about
MySQL and bugs in MySQL in public! These 5 years were mostly
I decided to celebrate with yet another post in this relatively new series and summarize in short what interesting things I studied, …
One of my customers wanted to migrate from an encrypted MySQL RDS instance to an encrypted Aurora instance. They have a pretty large database, therefore using mysqldump or a similar tool was not suitable for them. They also wanted to setup replication between old MySQL RDS and new Aurora instances.
Spoiler: this is possible without any logical dump.
At first, I checked Amazon’s documentation on encryption and found nothing about this type of …[Read more]
In this blog post, we’ll look at some of the MySQL high availability solution options.
In the previous post of this series, we looked at the MySQL high availability (HA) solutions that have been around for a long time. I called these solutions “the elders.” Some of these solutions (like replication) are heavily used today and have been improved from release to release of MySQL.
This post focuses on the MySQL high availability solutions that have appeared over the last five years and gained a fair amount of traction in the community. I chose to include this group only two solutions: Galera and RDS Aurora. I’ll use the term “Galera” generically: it covers Galera Cluster, MariaDB Cluster and Percona …[Read more]
I do not care much about MySQL 8.0.x at the moment, as it's far
from being GA and is work in progress. It is not yet used by
customers whom I have to support. But I know about many
interesting changes and improvements there that, eventually, are
going to influence all main forks and kinds of MySQL. So, it
would not be wise to ignore MySQL 8.0.c entirely even for
For this post I decided to briefly check what community reported bugs were fixed in the recent release, 8.0.2, based on release notes. For me it's a measure of community interest in MySQL 8.0.x and Oracle's interest in further working with MySQL Community. I ended up with the following, short enough list of bug fixes in the categories I usually care about (InnoDB, partitioning, replication and optimizer):
- The very first InnoDB bug mentioned in …
Actually, Mysqlbinlog tools can’t miner mysql binlog exactly correct.
In this post ,a special environment we got may hexadecimal characters what we don’t need.
Read this PDF: Special-code-rollback.pdf
TL;DR: unless you know what you are doing, you should always have a primary key on your tables when replicating in RBR (and maybe even all the time).
TL;DR2: MariaDB 10.1 has an interesting way to protect against missing a primary key (innodb_force_primary_key) but it could be improved.
A few weeks ago, I was called off hours because replication delay on all the slaves from a replication chain
orchestrator 3.0 Pre-Release is
now available. Most notable are
Raft consensus, SQLite backend
support, orchestrator-client no-binary-required
You may now set up high availability for
without need to set up high availability for
orchestrator's backend MySQL servers (such as
Galera/InnoDB Cluster). In fact, you can run a
orchestrator/raft setup using embedded
SQLite backend DB. Read on.
orchestrator still supports the existing shared
backend DB paradigm; nothing dramatic changes if you upgrade to
3.0 and do not configure
10 Older Entries »