How scheduler and script stand in supporting failover (Percona and Marco example) 

In part one of this series,  I had illustrated how simple scenarios may fail or have problems when using Galera native support inside ProxySQL. In this post, I will repeat the same tests but using the scheduler option and the external script.

The Scheduler

First a brief explanation about the scheduler.

The scheduler inside ProxySQL was created to allow administrators to extend ProxySQL capabilities. The scheduler gives the option to add any kind of script or application and run it at the specified interval of time. The scheduler was also the initial first way we had to deal with Galera/Percona XtraDB Cluster (PXC) node management in case of issues. 

…

How native ProxySQL stands in failover support (both v2.0.15 and v2.1.0)

In recent times I have been designing several solutions focused on High Availability and Disaster Recovery. Some of them using Percona Server for MySQL with group replication, some using Percona XtraDB Cluster (PXC). What many of them had in common was the use of ProxySQL for the connection layer. This is because I consider the use of a layer 7 Proxy preferable, given the possible advantages provided in ReadWrite split and SQL filtering. 

The other positive aspect provided by ProxySQL, at least for Group Replication, is the native support which allows us to have a very quick resolution of possible node failures.

ProxySQL has Galera …

Editor’s Note: Because our bloggers have lots of useful tips, every now and then we update and bring forward a popular post from the past. Today’s post was originally published on November 26, 2019.

It’s not uncommon these days for us to use a high availability stack for MySQL consisting of Orchestrator, Consul and ProxySQL. You can read more details about this stack by reading Matthias Crauwels’ blog post How to Autoscale ProxySQL in the Cloud as well as Ivan Groenwold’s post on MySQL High Availability With ProxySQL, Consul and Orchestrator. The high-level concept is simply that Orchestrator will monitor the state of the MySQL replication topology and report changes to Consul which in turn can update ProxySQL hosts using …

ProxySQL is proud to announce the latest release of ProxySQL version 2.0.15 on the 30th of October 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

ProxySQL v2.0.15 is a patch release comprising of minor backward compatible changes and bug fixes.

The most interesting highlight of this release is the introduction of ARMv8 64-bit packages which have been compiled for CentOS-RHEL 7/8, Debian 9/10 and Ubuntu 18/20 as well as a Docker image available on our …

Take advantage of the last training classes for the year and level up your ProxySQL skills for 2021!

Our public ProxySQL Total Training spans two days and will help you learn how to use ProxySQL’s features effectively and to efficiently deal with real life events and emergency situations that may occur in your infrastructure. This is instructor-led (our trainers not only build, but actively maintain ProxySQL) and is also hands on, so you will have exercises to complete.

The rich course content provides insights to help you build a solid understanding of ProxySQL’s design goals, and most importantly how to efficiently implement ProxySQL in order to maximize the resource utilization of your database cluster, while avoiding common pitfalls and anti-patterns!

Immerse yourself in the world of ProxySQL with our two-day ProxySQL Total Training.

ProxySQL Total Training topics …

For what reason should I use a real multi-primary setup?

To be clear, not a multi-writer solution where any node can become the active writer in case of needs, as for Percona XtraDB Cluster (PXC) or Percona Server for MySQL using Group_replication. No, we are talking about a multi-primary setup where I can write at the same time on multiple nodes. I want to insist on this “why?”.

After having excluded the possible solutions mentioned above, both covering the famous 99.995% availability, which is 26.30 minutes of downtime in a year, what is left?

Disaster Recovery? Well, that is something I would love to have, but to be a real DR solution we need to put several kilometers (miles for imperial) in the middle.

And we know …

Maybe one of the more “obscure” operations when dealing with replica lag, or, in general, when one needs to control writes to the database, is the Rate limit. It’s also lately one of the most popular conversations around the community.

But what is it? In plain words: holding up queries for a while, giving air to the replicas to breath and catch up. Something similar to the Galera’s Flow Control mechanism, although flow control, when it kicks in, stops all the writes while the nodes catch up. With a throttle no write is stopped, just delayed.

There are several ways to do this. A popular tool is Freno but this is also something that can be achieved with ProxySQL. Let’s see how.

Delay

ProxySQL has a variable called …

A blog series about ProxySQL and Galera…

This post is the first of a series of blogposts on how to easily use ProxySQL to scale-out your application’s database workload on a Galera cluster. This series will explore the main concepts in configuring ProxySQL for Galera across three articles as follows:

– A first introductory post describing the minimal configuration needed for ProxySQL to monitor and manage a Galera Cluster.
– A second post describing how to setup a read/write split configuration for our Galera Cluster, using ProxySQL query rules.
– A third and final post with examples on specific cluster configuration options and more detailed explanations on why and how ProxySQL changes the nodes states based on configuration changes and monitored variables. Requirements

To illustrate how to configure ProxySQL for a Galera Cluster we will use a sample Galera Cluster …

ProxySQL participará en la próxima edición del evento open source “ESLIBRE”, que tendrá lugar los días 18th & 19th de Septiembre. La fecha coincidirá con el “Software Freedom Day”, día que celebra el Free Software en el mundo entero.

El desarrollador senior de ProxySQL, Javier Jaramago Fernández, expondrá “Introducción a ProxySQL”, haciendo hincapié en la importancia de limitar el downtime tanto como sea posible, además de, exponer que otras herramientas ofrece ProxySQL y cómo podemos hacer uso de ellas para mejorar nuestra infraestructura.

La charla se centrará en ProxySQL como proyecto, sus características, y la topología básica de su uso.
Se expondrán ejemplos en tiempo real de cómo usar estas características, como:

• Cambios de configuración con Zero-downtime – ProxySQL posee tres capas de …

ProxySQL will be taking part in the upcoming EsLibre, open source event on the 18th & 19th of September. The date also coincides with ‘Software Freedom Day’ which celebrates Free Software, all over the world.

ProxySQL’s Senior Developer, Javier Jaramango Fernandez, will be discussing ‘Introduction to ProxySQL’, focusing on the importance of limiting downtime as much as possible, as well as, the tools ProxySQL offers and how you can use them to improve your infrastructure.

The talk will focus on the introduction of ProxySQL as a project, its characteristics, and the basic topology for its use.
Real-time examples and how to use them will also be discussed, such as:

• Zero-downtime configuration changes – ProxySQL offers three configuration layers: memory, disk and runtime. Each of these layers can be configured dynamically, …