Blog

Doing a search with InnoDB Cluster with DR (Disaster Recovery) yields lots of results, but does it actually work in the enterprise?

For MySQL and MariaDB database clusters, Saas, Fintech and other organizations with mission-critical databases typically require what’s called a managed “composite” cluster, or “cluster-of-clusters.” This blog is about active/active versus active/passive composite clusters for MySQL and MariaDB database systems.

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.

Welcome to the wonderful world of open source! You really are on your own, even if you think you acquire a solution that works. But many of the companies offering solutions based on open source components wrapped with expensive consulting engagements really can’t help you as they are not the original developers of some of the important core components, thus they do not have the necessary skills to fix them either.Welcome to the wonderful world of open source! You really are on your own, even if you think you acquire a solution that works. But many of the companies offering solutions based on open source components wrapped with expensive consulting engagements really can’t help you as they are not the original developers of some of the important core components, thus they do not have the necessary skills to fix them either.

Tungsten Replicator is the most advanced heterogeneous real-time data replication solution for MySQL, MariaDB & Percona Server, including Amazon RDS MySQL and Amazon Aurora. It provides high-performance and improved replication functionality over the native MySQL replication solution and into a range of target databases.

Following the announcement late last year that we’d made our flagship product Tungsten Cluster available on the Amazon Marketplace in an easy-to-access and deploy AMI format, we published some useful resources in the past few months to help users getting started with Tungsten Clustering in the AWS cloud.

This latest post on MySQL replication follows the ones we did on Amazon Redshift & Amazon Aurora; naturally, we had to cover Amazon RDS as well and so we look here at how to easily and securely replicate from MySQL to Amazon RDS (and vice versa).

Instead of contributing back to the original project, and in that way benefitting the project as a whole, Percona takes over smaller open-source projects (such as Galera) and larger open source projects (MySQL, MongoDB), then adds some small enhancements (especially when compared to the work done by the original developers), slaps its own name on it and proceeds to make some negative comments against those who have done the hardest work.

There are two key elements (which often separate us from many other open source operators, such as Percona) to our MySQL HA/DR and Continuous Operations solutions. Read this blog, adapted from the June “Word from the CEO” from the Continuent Newsletter to find out what distinguishes Continuent’s Tungsten Clustering solution in the open source MySQL database industry.

We often hear that asynchronous replication creates a possible data loss window, thus it is not an acceptable solution for certain types of applications.

Yes, this is true. In theory, that is. 

In practice, we have developed the Tungsten Cluster solution to the point that it really does not happen in real life. Please read this blog to understand why not!

SmartScale is a special mode of the Tungsten Connector (aka Tungsten Proxy), which allows read requests to be intelligently routed to either a replica or the primary to ensure that the data returned is not stale. This feature is available when the Connector is running in the application-layer Proxy mode. Learn more about the behavior of SmartScale in this blog.