Blog

When Tungsten Replicator extracts data, the information that has been extracted is written down into the Tungsten History Log, or THL.

In this blog, part of a series of “Recently a Customer Asked” posts for Tungsten University, we explore the reason for the occasional Tungsten Replicator OFFLINE:ERROR state when applying to AWS Redshift, along with possible steps to compensate for the issue.

This blog post discusses the Tungsten Replicator and how latency is calculated when extracting events on a Primary, and when applying events to the Replicas. We also examine what latency is, and the two different types of latency that we track - how to interpret them and how they differ.

In this blog post, we explore the new support for running Tungsten Dashboard via Docker containers. This method allows for a rapid configuration of the GUI. We describe the docker method of installing the Tungsten Dashboard using a pre-defined Docker container provided by Continuent containing Apache, PHP, HAProxy and the Dashboard.

In this blog post, we explore the 10 basic steps for doing a secure Tungsten Clustering deployment. A fresh Tungsten version 7 installation is secure by default. We also cover the various tungsten.ini options that impact an install.

In this blog post, we examine the “Broken Pipe” log message from the Tungsten Connector. We describe possible causes, and discuss the differences between Bridge and Proxy mode authentication methods.

In this blog post, we explore how the new Tungsten Replicator thl-applier role allows a Replica node to apply THL even when the upstream source Replicator is OFFLINE. This new behavior provides for better control and performance under a variety of conditions.

In this post we will explore new features in both tpm report and tpm ask in v7.1.0. Both commands will continue to evolve and grow over time. In this release we have added new information to the `tpm report` output when requested and new actions, arguments and keys for `tpm ask`.

Customers often use AWS to deploy MySQL or MariaDB Tungsten Clusters. This blog is about changing an AWS instance type from t2.large to t3.large specifically on Amazon Linux 1. It contains the steps to follow when changing AWS instance families to use enhanced networking.

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?"

Tungsten clustering supports a variety of topologies, each with unique characteristics. Today we introduce yet another compelling topology for your consideration: Tungsten Distributed Datasource Groups, with the new ability to failover automatically between Regions or Datacenters.

In this blog, part 6 of a series of “Recently a Customer Asked” posts for Tungsten University, we explore the reason for the dreaded "NOT A MEMBER" error when running the tpm command and possible root causes, along with steps to fix.