In this blog post, I’ll highlight new Backup Support in the MySQL Enterprise Backup 8.0 utility for Group Replication and InnoDB Cluster. This will also include usage of the MySQL login-path utility for accessing credentials for the backup process as highlighted in this other blog post on Devops ideas with MySQL and Scripting for Binary Log… Read More »
Features and capabilities continue to arrive in MySQL 8.0, most recently noted in the GA release of MySQL 8.0.13. The mysql-shell 8.0.12 release introduced a number of things, an important part was a cross-platform mysql-shell secure password handling facility. The MySQL Login-paths are a part of that security focus. Here we will look at where InnoDB Cluster 8.0,… Read More »
Let’s talk about MySQL high availability (HA) and synchronous replication once more.
It’s part of a longer series on some high availability reference architecture solutions over geographically distributed areas.
Part 2: MySQL High Availability On-Premises: A Geographically Distributed Scenario
The Problem
A question I often get from customers is: How do I achieve high availability in case if I need to spread my data in different, distant locations? …
[Read more]MySQL High Availability. Shutterstock.com
In this article, we’ll look at an example of an on-premises, geographically distributed MySQL high availability solution. It’s part of a longer series on some high availability reference architecture solutions over geographically distributed areas.
Percona consulting’s main aim is to identify simple solutions to complex problems. We try to focus on identifying the right tool, a more efficient solution, and what can be done to make …
[Read more]Version 8.0.12 added many great new features to MySQL. One of the new features included is the memory instrumentation of the XCom cache, which allows users to view and monitor the memory utilization of the cache by querying Performance Schema (PS).…
MySQL 8.0.13 improves replication lag monitoring by extending the instrumentation for transaction transient errors. These temporary errors, which include lock timeouts caused by client transactions executing concurrently as the slave is replicating, do not stop the applier thread: instead, they cause a transaction to retry.…
Enterprises require high availability for their business-critical applications. Even the smallest unplanned outage or even a planned maintenance operation can cause lost sales, productivity, and erode customer confidence. Additionally, updating and retrieving data needs to be robust to keep up with user demand.
Let’s take a look at how Tungsten Clustering helps enterprises keep their data available and globally scalable, and compare it to Amazon’s RDS running MySQL (RDS/MySQL).
Replicas and Failover What does RDS do?
Having multiple copies of a database is ideal for high availability. RDS/MySQL approaches this with “Multi-AZ” deployments. The term “Multi-AZ” here is a bit confusing, as enabling this simply means a single “failover replica” will be created in a different availability zone from the primary database instance. …
[Read more]One important way to protect your data is to keep your Tungsten Clustering software up-to-date.
A standard cluster deployment uses three nodes, which allows for no-downtime upgrades along with the ability to have a fully available cluster during maintenance.
Please note that with only two database cluster nodes, there is a window of vulnerability created by leaving zero failover candidates available when the lone slave is taken down for service.
The Best Practices: Staging Performing a No-Downtime Upgrade for a Staging Deployment
When upgrading a Staging-style deployment, all nodes are upgraded
at once in parallel via the tools/tpm update
command
run from inside the staging directory on the staging host.
No Master switch happens, and all layers are restarted to use the new code. …
[Read more]The MySQL Development Team is very happy to announce the second 8.0 Maintenance Release of InnoDB Cluster!
In addition to bug fixes, 8.0.13 brings some new exciting features:
- Defining the next primary instance “in line”
- Defining the behavior of a server whenever it drops out of the cluster
- Improved command line integration for DevOps type usage
Here are the highlights of this release!…
Tungsten Clustering is an extraordinarily flexible tool, with options at every layer of operation.
In this blog post, we will describe and discuss the two different methods for installing, updating and upgrading Tungsten Clustering software.
When first designing a deployment, the question of installation methodology is answered by inspecting the environment and reviewing the customer’s specific needs.
Staging Deployment Methodology
All for One and One for All
Staging deployments were the original method of installing
Tungsten Clustering, and relied upon command-line tools to
configure and install all cluster nodes at once from a central
location called the staging server
.
This staging server (which could be one of the cluster nodes) requires SSH access to all …
[Read more]