Blog

In this blog post, we will discuss how to use the Tungsten Connector keep-alive feature to ensure long-running MySQL & MariaDB/Percona Server client sessions stay connected in a Tungsten Cluster.

It is always a good idea to be mindful of open ports on your hosts, since they can be used by bad actors to gain access to your systems. For this reason, it is often desirable to prevent outside connections to the port whenever possible to prevent intrusions. For security purposes (and possibly PCI compliance), the Tungsten Connector proxy has the ability to bind to localhost/127.0.0.1 instead of listening on all available IP addresses via 0.0.0.0.

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

First step of the Tungsten overall “containerization” goal is achieved! The Continuent team wants to share with customers the Tungsten Proxy (originally Tungsten Connector) as a standalone service within a minimal Docker Image.

Sometimes you really, really want to know what a MySQL client is asking of the MySQL server. As of Tungsten Clustering v7.0.0, you may now enable Connector Audit Logging, which captures data transferred between client applications and MySQL servers to a file, database or socket. This blog post will walk you through the feature and how to enable, configure and disable Tungsten Connector Audit Logging.

SmartScale is a special mode of the Tungsten Connector (aka Tungsten Proxy), which allows read requests to be intelligently routed to either a replica or the primary to ensure that the data returned is not stale. This feature is available when the Connector is running in the application-layer Proxy mode. Learn more about the behavior of SmartScale in this blog.

Explore and de-mystify the various Tungsten Cluster Topologies. Get a clear understanding of each topology and how they compare.

Make It Smarter: Tuning MySQL Client Request Routing for Tungsten Connector