Blog

Replication is one of the most critical components of database management, especially in an Active-Active multi-primary composite cluster. However, with great flexibility comes the occasional hiccup. If you’re grappling with intermittent replication failures for a table in your Tungsten Cluster setup, here are five practical approaches to diagnose and resolve the issue.

Securing your cloud environment is now more critical than ever. As organizations increasingly rely on cloud platforms like Amazon Web Services (AWS), the potential for security breaches and unauthorized access becomes a pressing concern. AWS CloudTrail is a powerful tool that can help you monitor and detect suspicious activities in your AWS account. This blog post will guide you through the process of leveraging AWS CloudTrail to detect account intruders and strengthen your overall security posture.

Tungsten Clustering ensures high availability with robust failover capabilities, driven by the Tungsten Manager's health checks and predefined rules. In this blog post, we explore key processes like handling heartbeat gaps, network partitions, and availability checks. We also provide tips for tuning parameters to optimize performance and maintain a resilient database cluster.

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?

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 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: