Blog

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

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.

In this post, we will do a deep dive into how the Tungsten Replicator Parallel Applier works, and introduce a NEW filter for Parallel Apply called ShardByRulesFilter.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA version 7.0.2 are now available. Tungsten allows enterprises running business-critical MySQL database applications to cost-effectively achieve continuous global operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and geographically distributed active/active.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA versions 6.1.19 are now available. Tungsten allows enterprises running business-critical MySQL database applications to cost-effectively achieve continuous global operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and geographically distributed active/active.

Tungsten Replicator is a powerful tool with many great features, and today we will look at a new one - the ability to Pause and Resume a replication service. Until now, the only way to stop a replication stream was to take the service offline, and put it back online when it is needed again. The online process involves a number of internal steps and overhead, and if there are many THL files on disk, it could take some time to index them all before the service can come fully online. To remove the overhead of the startup time, the new pause/resume feature was developed for the Replicator, and is accessed via the `trepctl` command.

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA version 6.1.18 are now available. Tungsten allows enterprises running business-critical MySQL database applications to cost-effectively achieve continuous global operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and geographically distributed active/active.

In this blog, we discuss Galera Cluster and synchronous versus asynchronous replication. We also discuss some of the differences between Galera Cluster and Tungsten Cluster rooted in this difference in foundation. And how Tungsten has served a critical niche - mission-critical, geo-distributed, highly-performant MySQL applications - for a long time.