MySQL Cluster 7.6 is GA!
If you’re eager to give the recently announced MySQL Cluster 7.6 GA a spin, I’ll walk you through
a quick and simple way to get started using MySQL Cluster Manager 1.4.6.
Bootstrap and go!
That simple.…
It gives us great pleasure to announce that the 7.6 release of MySQL Cluster is now ready for prime time.
MySQL Cluster is the distributed database combining linear scalability and high availability. It provides in-memory real-time access with transactional consistency across partitioned and distributed datasets designed for mission critical applications.…
In the Replication QA team, we have been continuing to improve test coverage for Replication and Group Replication primarily to ensure that we support the newest and latest offerings of MySQL Server 8.0 such as Generated Columns, Set Persist, User Roles, and User Management DDLs that are now atomic.…
This post is about setting up MySQL InnoDB Cluster with 5 nodes
on a sandbox deployment. Here, we focus on implementation
part, the core concepts will be explained in separate posts.
Prerequisites:
Deploying MySQL InnoDB Cluster involves the following steps:
Deploying MySQL Engine:
If the MySQL engines are already installed on all the nodes, you
can skip this step and directly move into creating an InnoDB
Cluster part.
I am deploying 5 Sandbox instances (which is in-built on MySQL
Shell application) on a same …
There are lots of new features in MySQL 8.0 that was recently released including our Document Store capability. There are a few core capabilities related to InnoDB Cluster in 8.0 that I’d like to share but some will arrive in some coming blogs. Primarily here I’ll point out some nice details with InnoDB Cluster 8.0… Read More »
MySQL Cluster Manager 1.4.6 is now available for download from My
Oracle Support.
Overview
In MCM 1.4.6, the list backups command has been extended
with a new –agent option for listing agent backups
created with the backup agents command.
mcm> list backups --agent mysite; +------------+-------+---------+----------------------+---------+ | BackupId | Agent | Host | Timestamp | Comment | +------------+-------+---------+----------------------+---------+ | 1522914101 | 0 | tonfisk | 2018-04-05 07:41:41Z | | | 1522914105 | 0 | tonfisk | 2018-04-05 07:41:45Z | | | 1522914121 | 0 | tonfisk | 2018-04-05 07:42:01Z | | …[Read more]
We just published a series of 4 video tutorials about our native, full-stack, out-of-the-box and easy to use High Availability and Scaling solution for MySQL: InnoDB Cluster!
If you want to see the new MySQL Shell 8.0 in action to create a MySQL InnoDB Cluster and try it out yourself, just take a look!…
On March 22, 2018, we held a webinar on how Percona XtraDB cluster 5.7 (PXC) and ProxySQL can help achieve your database clustering high availability needs. Firstly, thanks to all the attendees for taking time to attend the webinar and we are sure you had a webinar experience. We tried answering some of your high availability questions during the call but due to time restrictions if we missed some of the questions then this blog will help clarify them.
Q. You say the replication to servers is virtually synchronous, if there is any latency, does ProxySQL detect this and select a node accordingly?
A. PXC nodes are …
[Read more]MySQL InnoDB Cluster has proven with the first GA release its potential as the native out-of-the-box HA solution for MySQL. With the second GA release, usability, stability and flexibility were greatly improved as described in the previous blog post.
This tutorial aims to show how does a typical InnoDB cluster setup look like and how that setup even became simpler and more effective as before.…
Introduction
In this post we will explore one approach to MySQL high
availability with HAProxy, Consul and Orchestrator.
Let’s briefly go over each piece of the puzzle first:
– HAProxy is usually installed on the application servers or an
intermediate connection layer, and is in charge of connecting the
application to the appropriate backend (reader or writer). The
most common deployment I’ve seen is to have separate ports for
writes (which are routed to the master) and reads (which are load
balanced over a pool of slaves).
– Orchestrator’s role is to monitor the topology and perform auto
recovery as needed.
The key piece here is how we can make HAProxy aware that a
topology change has happened, and the answer lies within Consul
(and Consul templates).
– Consul is meant to be told the identity of the new master by
Orchestrator. By leveraging Consul templates, we can then in turn
propagate that …
