Blog

Standards allow modern systems to advance, and the REST specification is one very important example. Since this post is about the Tungsten API in specific, let me simply say this - a RESTful API adheres to six principles: Client-server, stateless, cacheable, uniform interface, layered system and optionally code on demand. As part of the watchability/monitoring goal, our software as of version 7.0.0 includes a proper RESTful API - what we call APIv2. This API is fully documented and public.

Tungsten Clustering allows for many types of maintenance to happen with no downtime at all. This blog post will explore how to upgrade the actual MySQL Server on all cluster nodes with zero downtime. These same steps may be used to upgrade the MySQL server or patch the OS.

What are some strategies for improving performance when applying to a MySQL target database with Tungsten Replicator?

Prometheus and Grafana are open source tools that can be used for monitoring MySQL clusters. Prometheus can be used to collect metrics from MySQL clusters, and Grafana can be used to visualize the metrics. Starting with Tungsten v7, using the new Tungsten Prometheus Exporter feature, it’s become easy to leverage the best these powerful monitoring tools have to offer.

This post covers some standard Nagios checks that would help keep your Tungsten cluster nodes running MySQL / MariaDB / Percona Server healthy.

Your MySQL database cluster contains your most business-critical data; in this post, we discuss how to ensure proper performance under load.

In this blog post we explore various options for performance tuning MySQL server for better replica replication performance.

In this blog post we will define what a split-brain scenario means in a MySQL database cluster, and then explore how a Tungsten MySQL database cluster reacts to a split-brain situation.

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.

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.

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:

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.