Blog

Enterprises require high availability for their business-critical applications. Even the smallest unplanned outage or even a planned maintenance operation can cause lost sales, productivity, and erode customer confidence. Additionally, updating and retrieving data needs to be robust to keep up with user demand.

One important way to protect your MySQL / MariaDB / Percona Server data is to keep your Tungsten Clustering software up-to-date; but how can you achieve this with zero-downtime?

Learn about the two different methods for installing, updating and upgrading Tungsten Clustering software for MySQL / MariaDB / Percona Server.

We are growing!

Consequently, Continuent needs additional talented staff.

We are currently looking for a person who would be a good fit for our "Database Clustering Technical Sales & Support Engineer" position, in the US Pacific timezone.

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

In this AWS re:Invent talk excerpt, Tyler Turk (Infrastructure Engineer, Riot Games) discusses how the Riot team was able to migrate eight disparate database clusters into AWS as a single composite database cluster replicated in four different AWS regions, provisioned with terraform, and managed and operated by Ansible.

A robust monitoring setup is essential for cluster health and viability - if your replicator goes offline and you do not know about it, then that Replica becomes effectively useless because it has stale data. This means keeping a close watch on the health of the MySQL / MariaDB / Percona Server database nodes from many perspectives, from ensuring sufficient disk space to testing that replication traffic is flowing.

Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. The GUI makes the deployment much easier to visualize and administer.

The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.

In this blog post we will discuss one specific aspect of the THL (Transaction History Log) - the METADATA unsafe_for_block_commit flag.

Continuent is pleased to announce that Tungsten Dashboard v1.0.1 is now available!

Our Dashboard v1.0.1-36 is a bug fix release that also contains a few improvements. Some of the highlights include:

In this blog post, we discuss failover concepts and administration.

In this blog post, we describe the new Read Affinity tuning feature of the Tungsten Connector.

Tungsten Connector read affinity now supports multiple dataservices with ordering and exclusion (only one was previously allowed).

You may now fine-tune the affinity per user in user.map and via the global tpm configuration option connector-affinity.