Blog

People approach Continuent for many reasons, including: MySQL Continuous Operations: their business is using MySQL for business-critical applications that require zero downtime, including for maintenance updates MySQL Performance: their application performance and user experience are suffering due to a faltering MySQL backend MySQL Scaling and geo-scaling: they're scaling up and taking prudent preventative measures to lay a strong foundation based on anticipated growth, within region, cross the regions and

This blog article discusses why and how we use Ansible (automation tool for pre-configuring MySQL servers) for Tungsten purposes at Continuent, including a step by step description on how to use Ansible (including source code).

Over the past few days we have been working with a number of customers on the best way to handle Triggers within their MySQL environment when combined with Tungsten Replicator. This new blog dives head first into the minefield of Triggers and Replication.

The replicator is a critical piece of the Tungsten Clustering solution for MySQL / MariaDB, as well as its own stand-alone data replication product. Automatic recovery enables the replicator to go back online in the event of a transient failure. In this blog, we discuss how to enable Autorecovery.

How to move the Relay role to another node in a Composite Tungsten Cluster

Tungsten Clustering provides high availability, disaster recovery, and a host of other benefits for MySQL / MariaDB / Percona Server databases. In this blog post we will explore some of the shell aliases I use every day to administer various Tungsten Clusters.

Where are the logs for a Tungsten Cluster and which are the proper log files to monitor if I do a master role switch to another node?

Latency-sensitive applications running in Java sometimes experience unacceptable delays under heavy I/O load. This blog discusses why this problem occurs and what to do about it for applications running Tungsten Clustering for MySQL.

Background The Skinny

Performing schema changes often requires extended downtime for applications. This is due to MySQL needing to rebuild tables for common schema change operations. Tools like pt-online-schema-change have been written to try to overcome the downtime associated with schema changes, however they are complex and put a high load on the database.

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.