Shulou(Shulou.com)05/31 Report--

This article mainly introduces the common high-availability MySQL solutions, the article is very detailed, has a certain reference value, interested friends must read it!

1. Master-slave replication solution

The master-slave replication solution is a highly available solution provided by MySQL itself, and the data synchronization method uses MySQL replication technology.

MySQL replication is a log replication process in which one server acts as a master server and one or more other servers act as slave servers.

To put it simply, pull the binary log file from the server to the master server, and then parse the log file into the corresponding SQL and execute it again on the slave server.

The operation of the master server, in this way to ensure the consistency of the data.

MySQL replication technology only provides the synchronous execution function of the log, while the slave server can only provide read operations, and when the master server fails, it must pass the

To deal with the failover manually, the common practice is to change one from the server to the master server. This solution achieves the high availability of MySQL to some extent.

90% SLA (Service-Level Agreement) can be achieved.

In order to achieve higher availability, in the actual application environment, MySQL replication technology combined with highly available cluster software is generally used to achieve automatic failover.

95% of the SLA can be achieved in this way.

2. MMM High availability solution

MMM is the abbreviation of Master-Master Replication Manager for MySQL, the full name is MySQL master replication manager, which provides MySQL master replication

A scalable suite of scripts for monitoring, failover, and management of configuration. In the MMM high availability scheme, a typical application is a dual-master and multi-slave architecture, replicated through MySQL

The technology can realize that two servers are master and slave to each other, and only one node can be written at any time, which avoids the data conflict of multiple writes. At the same time, when available

When the master node fails, the MMM suite can monitor it immediately, and then automatically switch the service to another master node to continue to provide services, thus achieving the high availability of MySQL.

MMM solution is a mature high-availability solution for MySQL, which can achieve 99% SLA.

3.Heartbeat/SAN High availability solution

The Heartbeat/SAN high availability solution is implemented with third-party software and hardware. In this scenario, the way to handle failover is the highly available cluster software Heartbeat

It monitors and manages the network connected between each node, and monitors the cluster service. When the node fails or the service is unavailable, it automatically starts the cluster service in other nodes.

In the aspect of data sharing, the data is shared through SAN storage. In the normal state, the cluster master node will attach the storage for data reading and writing, but when the cluster fails

Heartbeat first releases the storage device attached to the primary node through an arbitration device, then mounts the storage on the standby node, and then starts the service in this way

Realize data sharing and synchronization. This kind of data sharing method is simple to implement, but the cost is high, and there is the possibility of brain fissure, so it needs to be chosen according to the actual application environment.

The scheme can achieve 99.99% SLA.

4.Heartbeat/DRBD High availability solution

The Heartbeat/DRBD high availability solution is also implemented with the help of third-party software and hardware, and Heartbeat is still used in the way of handling failover. the difference is that in data

In the aspect of sharing, the data synchronization software DRBD based on block level is used to realize it.

DRBD, or Distributed Replication Block Device, is a distributed storage replication of mirrored block device content between servers, which is implemented by software and has no sharing.

Solution. Unlike the SAN network, it does not share storage, but replicates data through the network between servers. This scheme is slightly more complex to implement, but also has brain fissure.

Problem, 99.9% SLA can be achieved.

5.MySQL Cluster High availability solution

MySQL Cluster is a technology that allows you to deploy the Cluster of an "in-memory" database in a system without sharing. With no shared architecture, the system can

Use cheap hardware and have no special requirements for hardware and software. In addition, because each component has its own memory and disk, there is no single point of failure.

MySQL Cluster consists of a group of computers, each running a variety of processes, including MySQL servers, NDB Cluster data nodes, and management servers

And (possibly) specialized data access programs.

MySQL Cluster consists of a group of service nodes, on which many processes are running, including MySQL server, NDB Cluster data node, and management server.

And special data access programs. This solution is the technical solution officially promoted by MySQL, which is powerful, but because of the tedious implementation process and troublesome configuration, the actual enterprise application

Not too much. The standard and telecom versions of MySQL Cluster (for telecom operators) can achieve 99.999% SLA.

These are all the contents of the article "what are the common high-availability MySQL solutions?" Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.