Blog

This blog post outlines our Continuent Tungsten pricing model for Tungsten Cluster software subscriptions and related 24/7 support.

AWS may reboot your Aurora database. What is the impact?

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.

Discover the latest enhancements, new features, and critical bug fixes in Tungsten Cluster and Tungsten Replicator version 7.1.2. Explore behavior changes affecting installation and deployment, learn about the introduction of the tungsten_mysql_ssl_setup command-line tool and critical bug fixes addressing issues such as data source monitoring and cluster switch failures.

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.

Continuent's flagship product, Tungsten Clustering v7, features significant improvements in usability, security, performance and connectivity for achieving seamless operational continuity of MySQL and MariaDB databases.

When external issues cause the primary extractor to go offline, we address the issue and bring the extractor back online. However, we need to make sure we start the extraction from the correct position so that the downstream replicas receive transactional data they require. Let’s determine the position and how we set it.

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.