From June 16th to 17th, the MySQL Team will be attending and speaking at the Hong Kong Open Source Conference 2018.
Unfortunately I won’t be present but some of my great colleagues will be speaking about MySQL.
If you are planning to attend HKOSCon2018, don’t miss their talks:
[Read more]Recently during my several talks and trips to meet the MySQL Community and MySQL InnoDB Cluster, I realized that some important message was missing. I got a lot of questions about which version of Router or Shell people should use. There is some confusion about which version to use, it seems that people thinks they should use MySQL Shell 1.0.x and MySQL Router 2.1.x with MySQL 5.7 and use the 8.0.x version having the same version as MySQL 8.0. This is wrong !
In fact, whatever the version of MySQL InnoDB Cluster you are using, you should ALWAYS use the latest version of Router and Shell. Currently it’s 8.0.11. So yes, even if you use MySQL 5.7.22, you MUST use MySQL Router 8.0.11 and …
[Read more]MySQL 8.0 became Generally Available (GA) on April 19th, a great moment for us working on MySQL at Oracle. It is now a “fully grown adult” packed with new features, and improvements to existing features, as described here.
This blog post focuses on the impact of replication performance improvements that went into MySQL 8.0.…
MySQL 8.0.11 seems to be around the corner and the new MySQL Shell will take advantage of all the new improvements made in MySQL 8.0 like SET PERSIST, RESTART, … see this previous post.
In the video below, I show you how easy it’s to deploy a MySQL InnoDB Cluster using the Shell that connects remotely to all the instances:
…
[Read more]Recently on MySQL Forums, somebody was looking for documentation or procedure to upgrade a MySQL InnoDB Cluster (or Group Replication cluster) to a newer version.
In this post I am illustrating the best practices to achieve this task safely.
To illustrate the procedure, I will use an InnoDB Cluster of 3
members: mysql1, mysql2 and
mysql3. The cluster is setup in Single-Primary mode
(mysql1) and runs MySQL 5.7.21.
Let’s have a look at the cluster status:
MySQL / mysql1:3306 / JS / cluster.status()
{
"clusterName": "MyCluster",
"defaultReplicaSet": {
"name": "default",
"primary": "mysql1:3306",
"ssl": "DISABLED",
"status": "OK",
"statusText": "Cluster is ONLINE and can tolerate up to …[Read more]
The latest release of dbdeployer is possibly the last one with a leading 0. If no serious bugs are found in the next two weeks, the next release will bear a glorious 1.0.
Latest news
The decision to get out of the stream of pre-releases that were published until now comes because I have implemented all the features that I wanted to add: mainly, all the ones that I wished to add to MySQL-Sandbox but it would have been …
[Read more]
Version 0.3.0 of dbdeployer has gained the ability of deploying
multiple sandboxes concurrently. Whenever we deploy a group of
sandboxes (replication, multiple) we can use
the --concurrent flag, telling dbdeployer that it
should run operations concurrently.
What happens when a single sandbox gets deployed? There are six sets of operations:
MySQL 8.0’s new default authentication plugin means more secure connections for users connections but also for replication… but you need to be aware of it !
Yesterday Giuseppe – the datacharmer – Maxia, submitted a bug related to a strange behavior of MySQL’s replication.
He observed that after creating a new user for replication (using
the new authentication method,
caching_sha2_password), when he created the slave as
usual, replication was not starting…
Slave_IO_Running was constantly in
“Connecting” and the Last_IO_Error was:
Last_IO_Error: error connecting to master 'repl2@127.0.0.1:24011' - …[Read more]
Where the hell is it?
The MySQL shell is a potentially useful tool that has been intentionally made difficult to use properly.
It was introduced, with much fanfare, with the MySQL Document Store, as THE tool to bridge the SQL and no-SQL worlds. The release was less than satisfactory, though: MySQL 5.7.12 introduced a new feature (the X-protocol plugin) bundled with the server. The maturity of the plugin was unclear, as it popped out of the unknown into a GA release, without any public testing. It was allegedly GA quality, although the quantity of bug reports that were filed soon after the release proved otherwise. The maturity of the shell was known as "development preview", and so we had a supposedly GA feature that could only be used with an alpha …
[Read more]
How it happened
A few years ago I started thinking about refactoring MySQL-Sandbox. I got lots of ideas and a name for the project (dbdeployer) but went no further. The initial idea (this was 2013!) was to rewrite the project in Ruby: I had been using Ruby at work and it looked like a decent replacement for Perl. My main problem was the difficulty of installation in an uncontrolled environment. If you have control over your environment (it's your laptop or you are in charge of the server configuration via Puppet or similar) then the task is easy. But if you ever need to deploy somewhere with little or no notice, it becomes a problem: there are servers where Perl is not installed, and is common that the server also have a policy forbidding all scripting languages from being deployed. …
[Read more]
