Blog

This blog is about testing time and test suites management. “Battle-tested” is the Continuent Tungsten QA (Quality Assurance) guarantee. Continuent Tungsten is a clustering and replication solution for MySQL and MariaDB used by some of the largest MySQL estates to achieve continuous MySQL operations, locally and globally (HA, DR and Geo Distribution). Besides the stellar support team, and fully-integrated components, customers say: “Stability,” and, “Tungsten just works.”

Performing MySQL schema changes often requires downtime for applications. In this blog, we cover two ways we can perform MySQL schema changes without risking downtime or other MySQL data problems. In this real-life customer example, we perform a schema change to modify the column data type from varchar(20) to varchar(50) on approx. 35 tables from 3GB to 10GB in size. Two of the tables are partitioned, and one of them is about 100GB combining all partitions for that table.

“We don’t take backups, we use replication instead.” If you happen to agree with this statement, I urge you to continue reading. But even if you think you have a good backup plan, I still urge you to continue reading. Taking backups is usually not one of the most exciting parts of the job, but it might be the part that saves your company from a catastrophe. So, let’s make a plan!

There are a number of MySQL HA solutions around. But there really is only one solution that Does MySQL HA Right!

Watch the replay of this webinar about geo-distributed active/active MySQL replication for Financial Services SaaS Providers and on how to guarantee credit card transaction availability with geo-distributed Tungsten MySQL clusters.

Explore and de-mystify the various Tungsten Cluster Topologies. Get a clear understanding of each topology and how they compare.

This blog discusses some best practices for using multiple filesystems on MySQL database servers and how to achieve the best performance with them, while avoiding some of the possible pitfalls.

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.

Watch the replay of a webinar with our colleagues from Datavail and hosted by DBTA during which we discuss whether “free” is really good enough for business-critical MySQL database environments.

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