After having explained how to achieve HA for MySQL Router for people who doesn’t want to install the MySQL Router on the application servers and after having illustrated how to use Pacemaker, this article explains how to setup HA for MySQL Router using keepalived.

Keepalived is very popular, maybe because it’s also very easy to use. We can of course use 2 or more servers. The principle is the same as on the previous articles, if the router dies, the virtual IP used by the application server(s) to connect to MySQL is sent to another machine where mysqlrouter is still running.

Let’s have a look at the configuration, in this case we use 2 machines, mysql1 and …

This article will explain how to setup HA for MySQL Router as described in a previous article about where should the router stand.

For this setup, I will use Pacemaker (part of RedHat High Availability Add-on and available on RHEL, CentOS, Oracle Linux, …).

Of course we need a MySQL InnoDB Cluster but we won’t really use it for the HA setup of the MySQL Router.

Installing Pacemaker

The first step is to install pacemaker on all the machines we will use for our “MySQL Router Cluster”:

# yum install pacemaker pcs resource-agents

Now we need to start the pcsd service and enable it at boot (on all machines):

# systemctl start pcsd.service 
# systemctl enable pcsd.service

It’s time now to setup authentication, this operation is again …

As you know, MySQL InnoDB Cluster is composed of 3 elements:

• a group replication cluster of at least 3 servers
• the MySQL Shell used to manage the cluster
• the MySQL Router that send the traffic from the application server(s) to the cluster

When presenting the solution in conferences, one the main question is Where should I put the router ? and the answer is always the same: the best place to install the router is the application server !

The router is a very lightweight process that gets its configuration from the cluster’s metadata and doesn’t require a lot of resources or maintenance.

So the ideal setup is the following:

However for many (obscure?) reasons, sometimes people doesn’t want to have the MySQL …

Welcome to the third part of this series. I’m glad you’re still reading, as hopefully this means you find this subject interesting at least. Previously we presented the first two components of MySQL InnoDB Cluster: Group Replication and MySQL Router and now we will discuss the last component, MySQL Shell.

MySQL Shell

This is the last component in the cluster and I love it. Oracle have created this tool to centralize cluster management, providing a friendly, command-line based user interface.

The tool can be defined as an advanced MySQL shell, which is much more powerful than the well known MySQL client. With the capacity to work …

Since MySQL 5.7 we have a new player in the field, MySQL InnoDB Cluster. This is an Oracle High Availability solution that can be easily installed over MySQL to get High Availability with multi-master capabilities and automatic failover.

This solution consists in 3 components: InnoDB Group Replication, MySQL Router and MySQL Shell, you can see how these components interact in this graphic:

In this three blog post series, we will cover each of this components to get a sense of what this tool provides and how it can help with architecture decisions.

Group Replication

This is …

As promised, here is a post more detailed on how to create a MySQL InnoDB Cluster using MySQL Shell and the AdminAPI.

First of all, as a good practice is never enough repeated, whatever the version of MySQL you are using, please use the latest MySQL Shell ! So if you are using 5.7, please use MySQL Shell 8.0.11. See this compatibility matrix or this official one.

dba class

The AdminAPI can be accessed by the MySQL Shell via the dba object. The reference manual for this class is here. The Shell …

Next week I will be speaking at DataOps in Barcelona about MySQL 8.0 Document Store. If you don’t know it yet, I really invite you to join this talk, you will be very surprised about all MysQL can do in the NoSQL world !

There will be also a lot other MySQL related sessions by many good speakers of the MySQL Community.

As I will be in Barcelona, the Barcelona MySQL Meetup invited me to give a session about MySQL InnoDB Cluster and Group Replication and I will also share the stage with my friend and colleague …

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:

• Heading to the New Stage of MySQL 8.0 – Ivan Ma
• Crossing Relation and Document Database using …

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 …

This post is about setting up MySQL InnoDB Cluster with 5 nodes on a sandbox deployment.  Here, we focus on implementation part, the core concepts will be explained in separate posts.

Prerequisites:

• MySQL Engine
• MySQL Shell
• MySQL Router

Deploying MySQL InnoDB Cluster involves the following steps:

• Deploying MySQL Engine (Sandbox Instance)
• Creating an InnoDB Cluster
• Adding nodes to InnoDB Cluster
• Configuring MySQL Router for High Availability.
• Testing High Availability.

Deploying MySQL Engine:

If the MySQL engines are already installed on all the nodes, you can skip this step and directly move into creating an InnoDB Cluster part.

I am deploying 5 Sandbox instances (which is in-built on MySQL Shell application) on a same …