Blog

The Question

Recently, a customer asked us:

Why would heavy disk IO cause the Tungsten Manager and not MySQL to be starved of resources?

For example, we saw the following in the Manager log file tmsvc.log:

Part of the power of Tungsten Clustering for MySQL / MariaDB is its intelligent MySQL Proxy, known as the Tungsten Connector. Tungsten Connector has three main modes, and depending on the type of operations you are performing (such as if you need read-write splitting), we help you choose which mode is best. Hence the question, "How can I tell which Tungsten Connector mode I am using: Bridge, Proxy/Direct or Proxy/SmartScale?"

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

This blog explores the best practices for deploying Tungsten Clustering for MySQL across Availability Zones, outlining the approaches for best high availability, fast response times, and load balancing recommendations.

Where are the logs for a Tungsten Cluster and which are the proper log files to monitor if I do a master role switch to another node?

In this blog post we discuss importing CSV data into a Tungsten Cluster.

Latency-sensitive applications running in Java sometimes experience unacceptable delays under heavy I/O load. This blog discusses why this problem occurs and what to do about it for applications running Tungsten Clustering for MySQL.

Background The Skinny

Performing schema changes often requires extended downtime for applications. This is due to MySQL needing to rebuild tables for common schema change operations. Tools like pt-online-schema-change have been written to try to overcome the downtime associated with schema changes, however they are complex and put a high load on the database.