Blog

Learn how to rotate MySQL SSL/TLS certificates with zero downtime using Tungsten Clustering 7.2.0/8.0.1 and the tpm cert tool, including generating certs, dual-alias rollout, safe node-by-node restarts, SELinux fixes, and cleanup to retire old aliases without interrupting production.

Learn how to implement advanced MySQL health checks for HAProxy using systemd socket-based activation. Execute custom SQL queries for deeper database verification before routing traffic, replacing shallow TCP probes with intelligent failover decisions.

Learn how the Continuent team designed a secure and effective REST API for Tungsten Clustering, including best practices for using POST, PUT, verbs, idempotent actions, and more in real-world scenarios.

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.