MySQL InnoDB Cluster: is the router a single point of failure ?

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 Router on the same server as the application server and would like to have it on its own server instance (let’s hope they are not VM on the same physical machine 😉 ). Of course this setup is possible as illustrated below, but then, yes in that specific case, the router is a spof (Single Point Of Failure). Which means that if the router or the server where the router is installed crashes, none of your application servers are able to contact the database anymore:

If you really want to have such setup, you will have to setup HA for the MySQL Router. Such HA setup is very dependent of your  infrastructure as you may have to play with virtual IPs and this is not managed the same way on Linux and Windows for example.

So if you want to install the MySQL Router on another place than the recommended application server, you will have to take care by yourself of the router’s HA.

Of course they are plenty solution to achieve such HA setup for the MySQL Router and I will try to illustrate some of them on this blog. The next article on the topic will be How to setup MySQL Router HA with Pacemaker, dont’ miss it 😉


The principle is simple, you will have multiple resources (the MySQL Router) running on multiple machines (at least more than one), and a VIP (virtual IP) resource that the application will use to connect to the router. If the “router resource” where the VIP resource runs, crashes, the VIP will be moved automatically to another server/node where the “router resource” is available:

If the router goes away, then the VIP is sent to another nodes:

Of course, if your application can use some round-robin (most of the MySQL Connectors allows that), you can have multiple VIP resources like this:


If you follow the recommendation, the MySQL Router is not a single-point-of-failure, but if you want to have it on its own server, then you will have to setup HA for it as this is very dependent of your infrastructure.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.


  1. If a host name has a DNS name record with more than one ip address the mysql client will try to connect to any of the addresses configured.

    The other more explicit configuration setup could be handled with: which for situations like this would be really useful.

    So pacemaker and other techniques also work but I would love the client to be able to use DNS SRV records as this would simplify the HA configuration significantly for situations like the one you mention.

  2. I have been researching with MySQL InnoDB and came to know about the cluster of a router. This came to be of great help for my work. I have learned a lot of thing from the blog. I am very much helpful to the author of the post for sharing such a great article with us.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

As MySQL Community Manager, I am an employee of Oracle and the views expressed on this blog are my own and do not necessarily reflect the views of Oracle.

You can find articles I wrote on Oracle’s blog.