I have not much yet to say on a popular topic of upgrading everything to MySQL 8, so let me just continue reviewing public MySQL bug reports that I've subscribed to recently. After my previous post at least one bug, Bug #94747, got enough comments and clarifications (up to specific commit that introduced this regression pointed out by Daniel Black!) to have it re-classified and verified as InnoDB code bug. So, I see good reasons to continue attracting wide public attention …[Read more]
10 Older Entries »
Everywhere I go to present MySQL InnoDB Cluster, during the demo of creating a cluster, many people doesn’t understand why when I’ve 2 members, my cluster is not yet tolerant to any failure.
Indeed when you create a MySQL InnoDB Cluster, as soon as you have added your second instance, you can see in the status:
"statusText": "Cluster is NOT tolerant to any failures.",
Why is that ? It’s because, to be part of primary partition (the partition that holds the service, the one having a Primary-Master in Single Primary Mode, the default mode), your partition must reach the majority of nodes (quorum). In MySQL InnoDB Cluster (and many other cluster solutions), to achieve quorum, the amount of members in a partition must be > (bigger) than 50%.
So when we have 2 nodes, if there is a network issue between …[Read more]
I've got few comments to my post on references to MariaDB in MySQL bug
reports (not in the blog, but via social media and in personal messages), and all
but one comments from current and former colleagues whose opinion
I value a lot confirmed that this really looks like a kind of
attempt to advertise MariaDB. So, from now on I'll try to keep my
findings on how tests shared by MySQL bug reporters work in
MariaDB for myself, MariaDB JIRA and this blog (where I can and will
advertise whatever makes sense to me), and avoid adding them to
MySQL bug reports.
That said, I still think that it's normal to share links to MariaDB bug reports that add something useful (like patches, …
When I designed dbdeployer, I wanted to eliminate most of the issues that the old MySQL-Sandbox had:
- dependencies during installation
- mistaken tarballs
- clarity of syntax
- features (un)awareness.
Dependencies during installation did go away right from the start, as the dbdeployer executable is ready to be used without additional components. The only dependency is to have a host that can run MySQL. There is little dbdeployer can do about detecting whether or not your system can run MySQL. It depends on which version and flavor of MySQL you are running. It should not be a big deal as I assume that anyone in need of dbdeployer has already the necessary knowledge about MySQL …[Read more]
Why migrating to MySQL 8.0 ?
MySQL 8.0 brings a lot of new features. These features make MySQL database much more secure (like new authentication, secure password policies and management, …) and fault tolerant (new data dictionary), more powerful (new redo log design, less contention, extreme scale out of InnoDB, …), better operation management (SQL Roles, instant add columns), many (but really many!) replication enhancements and native group replication… and finally many cool stuff like the new Document Store, the new MySQL Shell and MySQL InnoDB Cluster that you should already know if you follow this blog (see these TOP 10 for features for developers and this TOP 10 for DBAs & OPS).
Not anymore a drop in replacement !
Why migrating to MySQL 8.0 ?
MySQL 8.0 brings a lot of new features. These features make MySQL database much more secure (like new authentication, secure password policies and management, …) and fault tolerant (new data dictionary), more powerful (new redo log design, less contention, extreme scale out of InnoDB, …), better operation management (SQL Roles, instant add columns), many (but really many!) replication enhancements and native group replication… and finally many cool stuff like the new Document Store, the new MySQL Shell and MySQL InnoDB Cluster that you should already know if you follow this …[Read more]
This is why MySQL supports now (since 8.0.14) a new consistency model to avoid such situation when needed.
Nuno Carvalho and Aníbal Pinto already posted a blog series I highly encourage you to read:[Read more]
MySQL InnoDB Cluster is evolving very nicely. I realized that the MySQL Shell also improved a lot and that it has never been so easy to setup a cluster on 3 new nodes.
This is a video of the updated procedure on how to install MySQL InnoDB Cluster on GNU Linux rpm based (Oracle Linux, RedHat, CentOS, Fedora, …)
Two weeks passed since my previous review of public MySQL bug reports I
consider interesting enough to subscribe to them. Over this
period I picked up a dozen or so new public bug reports that I'd
like to briefly review today.
Here is my recent subscriptions list, starting from the oldest bug reports:
- Bug #94431 - "Can't upgrade from 5.7 to 8.0 if any database have a hyphen in their name". It seems one actually needs a database like that created in MySQL 5.6 with at least one InnoDB table having FULLTEXT index to hit the problem. Great finding by Phil Murray. Note that after several unsuccessful attempts by others the bug was eventually reproduced and verified by …
Today I'd like to continue my review of public MySQL bug reports with a
list of some bugs I've subscribed to over last 3 weeks. It's
already long enough and includes nice cases to check and share.
Note that I usually subscribe to a bug either because it directly
affects me or customers I work with, or I consider it technically
interesting (so I mostly care about InnoDB, replication,
partitioning and optimizer bugs), or it's a "metabug" - a problem in the way public bug report
is handled by Oracle engineers. These are my interests related to
As usual, I start with the oldest bugs and try to mention bug reporters by name with links to their other reports whenever this may give something useful to a reader. I try …
10 Older Entries »