Recently, a Continuent customer asked: “What is your approach for scaling up MySQL clusters for a higher number of queries per second and larger data sets?” Scaling, like availability, is a multifaceted question. In this blog post we will detail and discuss the best practices for scaling Tungsten Clusters.
In this blog post we examine in depth how to best provision one MySQL database cluster node from another using rsync. Since there are many possible ways to handle provisioning by rsync, we will do multiple posts on the topic, starting with the most basic - both the source and target database nodes are fully offline for the duration of the rsync. While this is not an ideal scenario because two nodes are down at once, it does allow one replica to be provisioned from another replica when all else fails.
Galera Cluster provides high availability and scalability for MySQL. While this provides high availability in a local region or site, it does not provide any provisions for disaster recovery (DR) or any multi-site deployment in general, so let’s explore how we could extend the functionality of Galera Cluster to deploy at geo-scale.
Recently a customer asked, “Are there any issues with running a specific node with parallel apply enabled, and the rest of the nodes using a single stream (parallel disabled)? Just curious because that would be easiest for A/B testing of the replication effects.” Firstly, the answer is yes, you may certainly enable Parallel Apply on a single node within a Tungsten Cluster.
In this blog post we explore the implications and best practices for using Parallel Apply in this way.
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.
Oracle MySQL InnoDB Cluster provides high availability and scalability for MySQL. An InnoDB Cluster consists of 3 or more MySQL instances in a local network with group replication enabled, MySQL Shell which is used for management of the cluster, and optionally MySQL Router to provide basic routing from applications to the cluster. While this provides high availability in a local region or site, it does not provide any provisions for disaster recovery (DR) or any multi-site deployment in general, so let’s explore how we could extend the functionality of InnoDB Cluster to deploy at geo-scale.
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.”
Prometheus is one of the more popular ways to monitor your resources, and starting with version 7.0.0, Continuent has embedded the Prometheus exporter functionality into our core MySQL and MariaDB clustering products. This blog post covers how to enable the exporters, getting metrics and what metrics are available, along with cli tools, customizing the config, documentation references and a little bit about Grafana Dashboard for Tungsten Clusters.
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.
