Blog

In this blog post, we talk about how to configure automatic start at boot time for the Tungsten Clustering components.

By default, Tungsten Clustering does not start automatically on boot. To enable Tungsten Clustering to start at boot time, use the deployall script provided to create the necessary boot scripts:

Join MC Brown, VP Products at Continuent, on August 8th for our new webinar on high availability and disaster recovery for MySQL, MariaDB and Percona Server with Tungsten Clustering.

Tungsten Connector is an essential part of Tungsten Clustering for MySQL, MariaDB, and Percona Server. In this blog post, we talk about the Automatic Reconnect feature in the Tungsten Connector. Automatic reconnect enables the Connector to re-establish a connection in the event of a transient failure.

In this blog post, we talk about how existing client connections are handled by the Tungsten Connector when a manual master role switch is invoked and how to adjust that behavior. Tungsten Connector is an intelligent proxy that serves an essential role in Tungsten Clustering for MySQL, MariaDB, and Percona Server.

The Tungsten Connector is an intelligent MySQL proxy that provides key high-availability and read-scaling features. This includes the ability to route MySQL queries by inspecting them in-flight.

Tungsten Connector is an intelligent proxy used in Tungsten Clustering for MySQL / MariaDB / Percona Clustering. In this blog post, we talk about how query connections are handled by the Tungsten Connector, especially read-only connections.

This blog post covers global MySQL / MariaDB / Percona Server clustering with Active/Active meshed replication, the architecture commonly used for globally-distributed SaaS companies.

What if I want the cluster to be less sensitive to network, especially WAN latency?

Missed our Tungsten Clustering 6.0 webinar and technical deep di

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

Our 6.0.2 release is a critical bug fix for the cluster Manager logic within a Multimaster cluster.

All current users of v6.0.0 and v6.0.1 should upgrade IMMEDIATELY!

Fixes issue CT-672: the manager could set the master to read-only when performing a switch operation.

There is a procedural work-around if you get into this situation:

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

We are pleased to announce that Tungsten Clustering 6.0.1 and Tungsten Replicator 6.0.1 are now available!