Blog

This blog covers INI vs Staging configurations for Secure Shell.

In this blog post we will discuss how to best integrate various Continuent-bundled cluster monitoring solutions with PagerDuty (pagerduty.com), a popular alerting service.

Our colleague Matt Lang walks you through a comparison of building a global, multi-region MySQL / MariaDB / Percona cloud back-end using AWS Aurora versus Continuent Tungsten.

In case you missed the Multimaster webinar recorded live on Thursday, March 28th, 2019:

Learn how NewVoiceMedia built a global, multi-region MySQL cloud back-end to support a high-volume cloud contact center.

Continuent is pleased to announce that Tungsten Clustering 6.0.5 and Tungsten Replicator 6.0.5 are now available!

Our v6.0.5 release fixes a number of bugs and introduces some new features, with improvements across the board in a variety of different components.

Some of the key improvements include:

Learn how to build a global, multi-region MySQL / MariaDB / Percona cloud back-end capable of serving hundreds of millions of online multiplayer game accounts:

Watch the Replay

Continuent is pleased to announce that Tungsten Clustering 5.3.6 and Tungsten Replicator 5.3.6 are now available!

Our 5.3.6 release fixes a number of bugs and has been released to improve stability.

Highlights common to both products:

Clickhouse is a relatively new analytics and datawarehouse engine that provides for very quick insertion and analysing of data. Like most analytics platforms it's built on a column-oriented storage basis and unlike many alternatives is completely open source. It's also exceedingly fast, even on relatively modest platforms.

Continuent is pleased to announce that Tungsten Clustering 6.0.4 and Tungsten Replicator 6.0.4 are now available!

Our v6.0.4 release fixes a number of bugs and introduces some new features, with improvements across the board in a variety of different components.

Some of the key improvements include:

When deploying Tungsten Clustering for MySQL / MariaDB / Percona Server, we always recommend an odd number of Manager nodes in each cluster. Let's take a look at how having an odd number of Managers helps keep a Tungsten Cluster functioning and avoids data corruption scenarios (i.e. "split brain").

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

You already know about the Tungsten Connector which is the "secret sauce" that routes your application database traffic to the appropriate MySQL data source of your cluster. Have you ever wondered how the Connector keeps track of the cluster configuration? How it always knows which host is the master (or masters in a Composite Multimaster topology), and which are slaves?