24/7/365 Support

We are pleased to announce that Tungsten Clustering and Tungsten Replicator GA versions 6.1.16 are now available. Tungsten allows enterprises running business-critical MySQL database applications to cost-effectively achieve continuous global operations with commercial-grade high availability (HA), geographically redundant disaster recovery (DR) and geographically distributed active/active.

The tungsten_merge_logs command is designed to aid troubleshooting by consolidating the various log files into one place (merged.log), ordered by time. There are many moving parts to a cluster and they are spread over multiple nodes (usually three). When there is an issue, the logs are the key resource to find out what is going on. The best practice is to gather the log files into one place and then read through them all. This can be difficult with many files on multiple nodes. For this reason, the `tungsten_merge_logs` tool was created.

“How can I simulate a failure of the Active half of an Active/Passive Cluster to test the Failover to the Passive half?”

In this blog post we explore the best practices for simulating a failure of the Active cluster in an Active/Passive Composite Cluster.

As we are all being pushed to the limit to meet unprecedented demands online, the pandemic shined a light on many new frontiers and achievements in technology. This blog is about continuous MySQL database operations when you have a global user base, particularly the VMworld 2021 Global Multi-Cloud conference.

MySQL High Availability (HA) is typically what architects and technologists look for in building business-critical and mission-critical applications, and they aspire to measure MySQL uptime in 4 or preferably more “nines.” This blog explores the modern world of continuous MySQL operations - cross-region, global, hybrid-cloud, and multi-cloud - and why you might need a different approach.

A short contemplation about the current state of the programming languages. What language to choose for a new project? What are the differences between them? Is there a best language for everything?

If Continuent Support was depicted as a cartoon character, who would you choose? I know who I would choose...I’ll give you a clue...Very Fast...Beep Beep…

In this blog we will explore Continuent Support...What we do, how we do it and the tools available to the customer that make all that happen at lightning speed.

On August 20th, 2020 we released v6.1.6 of our Tungsten Clustering and Tungsten Replicator products. On August 17th, 2021, we released v6.1.14. In this blog we take a look back over the last 12 months and highlight some of our key updates and fixes.

This blog is about Bug Hunting. “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.”

“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 and uptime; why? Besides the stellar support team, and fully-integrated components, customers say: “Stability,” and, “It just works.”“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 and uptime; why? Besides the stellar support team, and fully-integrated components, customers say: “Stability,” and, “It just works.”

This blog is the first blog in a new series about Tungsten’s QA (Quality Assurance). 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 and uptime; why? Besides the stellar support team, and fully-integrated components, customers say: “Stability,” and, “It just works.”

This blog is about troubleshooting failed DDL across all Replicas in a composite active/active (CAA) Tungsten Cluster. The issue was resolved by setting a more permissive SQL_MODE, then locating and cleaning the bad data with proper NULLs before re-issuing the ALTER TABLE.