Well, since working with outdated clusters and upgrade paths that quickly become obsolete, as in my last post, Migrating/importing NDB to Cluster Manager w/ version upgrade. , I wanted to share that we can also use Cluster Manager, mcm, to upgrade NDB Cluster from 7.3 directly to 7.5. So we can start using the mcm new features like autotune that help guide us towards some Cluster tuning, or 7.5 new features like READ_BACKUP or FULLY_REPLICATED tables. …
[Read more]Percona announces the release of Percona Monitoring and Management 1.2.2 on August 23, 2017.
For install and upgrade instructions, see Deploying Percona Monitoring and Management.
This release contains bug fixes related to performance and introduces various improvements. It also contains an updated version of Grafana.
Changes in PMM Server
We introduced the following changes in PMM Server 1.2.2:
Bug fixes¶
-
PMM-927: The error …
I’ve had some questions from people using MySQL Cluster GPL and wanting to move to using MySQL Cluster Carrier Grade Edition, i.e., they want to use MySQL Cluster Manager, MCM, to make their lives much easier, in particular, upgrading (as well as config change ease and backup history).
All I want to do here is to share with you my personal experience on migrating what’s considered a ‘wild’ NDB Cluster to a MCM managed cluster. It’s just as simple to follow the manual chapter Importing a Cluster into MySQL Cluster Manager so at least you can see how I did it, and it might help someone.
[ If you’re not migrating but just looking for further information on NDB Cluster, and came across this post, please please PLEASE look at the …
[Read more]Percona announces the release of Percona Monitoring and Management 1.2.1 on August 16, 2017.
For install and upgrade instructions, see Deploying Percona Monitoring and Management.
This hotfix release improves memory consumption.
Changes in PMM Server
We’ve introduced the following changes in PMM Server 1.2.1:
Bug fixes
-
PMM-1280: PMM server affected by nGinx CVE-2017-7529. An …
In this blog post, I’ll look at a trick we use at Percona when upgrading to MySQL 5.7.
I’ll be covering this subject (and others) in my webinar Learning MySQL 5.7 on Wednesday, July 19, 2017.
We’ve been doing upgrades for quite a while here are Percona, and we try to optimize, standardize and improve this process to save time. When upgrading to MySQL 5.7, more often than not you need to run REPAIR or ALTER via mysql_upgrade to a number of MySQL tables. Sometimes a few hundred, sometimes hundreds of thousands.
One way to cut some time from testing or executing mysql_upgrade is to combine it with mysqlcheck. This identifies tables that need to be rebuilt or repaired. The first …
[Read more]
Long time no post.... :-)
Here's something interesting.
Last week I decided to give MySQL 5.7 a try (yes, I am kinda
conservative DBA...) and the very same day that I installed my
first 5.7 replica I noticed that, after changing my own password
on the 5.6 master, I could no longer connect to the 5.7
slave.
Very annoying, to say the least! So I went and dug out the root
password (which we do not normally use) and when I connected to
the slave I was surprised to see that my password's hash on the
5.7 slave was different than the hash on the 5.6 master. No
wonder I couldn't connect....
A bit of research on the MySQL documentation and I understood
that 5.7 introduced few changes around the way you work with
users' passwords. SET PASSWORD is now deprecated in favour
of ALTER USER: see MySQL 5.7 Reference Manual …
For the impatient:
# echo -e "deb http://repo.mysql.com/apt/debian/ stretch mysql-5.7\ndeb-src http://repo.mysql.com/apt/debian/ stretch mysql-5.7" > /etc/apt/sources.list.d/mysql.list # wget -O /tmp/RPM-GPG-KEY-mysql https://repo.mysql.com/RPM-GPG-KEY-mysql # apt-key add /tmp/RPM-GPG-KEY-mysql # apt update # apt install mysql-server
In the latest stable version of Debian, if you ask to install mysql-server, you now get installed mariadb automatically, with no (evident) way of installing Oracle’s MySQL. Any major version upgrade has to be done carefully (not only for MariaDB, but also for MySQL and Postgres), and I bet that a MySQL 5.5 to MariaDB 10.1 will cause a huge confusion. Not only it will fail user expectations, I think this will cause large issues now that MariaDB has chosen to become a “hard” fork, and become incompatible in many ways with MySQL. Not only the server upgrade will cause user struggle, the connector is …
[Read more]Disclaimer: This post is aimed to you, the curious developer, sys-admin, technologist, whatever-title-you-use. DO NOT run the following lines on production. Not even in a stable environment, do this if you don’t care about the outcome of the current data.
If you want to keep up with the newest MySQL developer milestones I have news for you: there is no upgrade available for milestone versions. The way to go is to remove old version and install new one, according to their website:
Upgrades between milestone releases (or from a milestone release to a GA release) are not supported. For example, upgrading from 8.0.0 to 8.0.1 is not supported, as neither are GA status releases.
So if you, like me, had the 8.0.0 version and want to test the 8.0.1 (alhtough 8.0.3 milestone is already in development) …
[Read more]Here’s a step-by-step guide on how to invert roles for master and slave so you can perform a master server upgrade, and then switch roles back to the original setup.
* While following this guide consider server-A as your original master and server-B as your original slave. We will assume server-B already produces binlogs and that both nodes have log-slave-updates=1 in my.cnf
Check this following link for more details on
log-slave-updates: https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_log-slave-updates
1. Prepare the original Slave to invert roles.
Make sure the slave is …
[Read more]
MySQL 5.7 comes with many changes. Some of them are better
explained than others.
I wanted to see how many changes I could get by comparing SHOW
VARIABLES in MySQL 5.6 and 5.7.
The most notable ones are:
- binlog_format: the default is now ROW. This variable affects the format of the binary log, whether you use it as a backup complement or for replication, the change means bigger binary logs and possibly side effects.
- …