Blog

While the MySQL Auto-Reconnect feature is both handy and interesting, it has to be used with great care, along with an understanding of the behavioral implications and side effects. In this blog post we will discuss some of the risks of using the MySQL driver Auto-Reconnect feature, and what happens when the Tungsten Connector internal version of it is enabled.

One nice thing about Tungsten Clustering is that you need just a single command to move the primary role to another host in your cluster.

This blog discusses some of the ways you can configure your MySQL / MariaDB / Percona Server replicas using Tungsten Clustering.

Need to do maintenance on a host? Learn how to suspend it gracefully.

Want your application to read from replicas? Here is how to choose the best r/w splitting option available in Tungsten Clustering.

How to pass arguments from an application to a database proxy, per-connection, to a Tungsten Database Proxy using connection parameters.

Thinking transparent reconnects of applications is the grail of HA? It is! But Active/Active setups make them risky.

How the Continuent Proxy selects database cluster nodes for executing read operations.

Database Proxies provide a single entry point into MySQL for the calling client applications. Proxies are wonderful tools to handle various situations like a master role switch to another node for maintenance, or for transparency with read and write connections. However, when the time comes to perform the switch action, all of the calling clients have been funneled through the proxy, so identification of the calling host from the database itself becomes difficult.

When it comes to zero downtime, proxies are the first line components of a cluster. In order to achieve High Availability (HA) for MySQL, MariaDB and Percona Server, a commonly deployed setup consists of configuring load balancers (hardware or software) on top of those proxies.

You already know about the Tungsten Connector which is the "secret sauce" that routes your application database traffic to the appropriate MySQL data source of your cluster. Have you ever wondered how the Connector keeps track of the cluster configuration? How it always knows which host is the master (or masters in a Composite Multimaster topology), and which are slaves?

Achieving software upgrades without downtime is a challenge that few software products can handle, or even try to. Tungsten Clustering is one that can!