MySQL application layer high-availability system and method suitable for various cloud environments

Abstract

The invention discloses a MySQL application layer high-availability system and method suitable for various cloud environments. The system comprises a plurality of MySQL instance units; a guard unit used for checking whether the MySQL instance units are healthy or not; a state storage unit used for storing the state information of the MySQL instance unit according to the inspection result of the guard unit, and setting a switching mark if the MySQL instance unit is unhealthy; a switching unit used for closing the connection of the unhealthy MySQL instance units and creating the connection of the healthy MySQL instance units; and a switching detection unit used for detecting the switching sign at regular time, and calling the switching unit to trigger switching if the switching sign is found. MySQL high availability, simple architecture, dual-node-based dual-master replication, adaptation to various cloud environments, online use in a plurality of cloud machine rooms, rapid switching, noinfluence on services and no perception of users are realized in the application layer.

Description

technical field [0001] The invention belongs to the technical field of computers, and in particular relates to a MySQL application layer high-availability system and method applicable to various cloud environments. Background technique [0002] There are currently four common methods for MySQL high availability: the first method, dual-node master-slave + keepalived / haproxy; the second method, MHA+ multi-node cluster; the third method, zookeeper+proxy; the fourth method, SAN shared storage. [0003] The first method (dual-node master-slave + keepalived / haproxy) has a simple architecture and direct switching between two nodes. The disadvantage is that additional consideration needs to be given to the high-availability mechanism of haproxy and keepalived, especially in the cloud environment, because it has been virtualized, it is often not used. Support keepalived. [0004] The second method (MHA+ multi-node cluster) can automatically detect and transfer faults, and has bette...

AI Technical Summary

Problems solved by technology

[0003] The first method (dual-node master-slave + keepalived / haproxy) has a simple architecture and direct switching between two nodes. The disadvantage is that additional consideration needs to be given to the high-availability mechanism of haproxy and keepalived, especially in the cloud environment, because it has been virtualized, it is often not used. support keepalived

[0004] The second method (MHA+ multi-node cluster) can automatically detect and transfer faults, and has better scalability. The probability of three-node / multi-node MySQL being unavailable is lower. The disadvantage is that it requires more resources than two-node ;The logic is more complicated, and it is more difficult to troubleshoot and locate the problem after a fault occurs; it may be caused by a split-brain phenomenon due to network partition

[0005] The third method (zookeeper+proxy) better guarantees the high availability of the entire system and has better scalability. The disadvantage is that the logic of the entire system becomes more complicated when ZK is introduced.

[0006] The fourth method (SAN shared storage) only needs two nodes, simple deployment, simple switching logic; very good guarantee of strong data consistency; the disadvantage is that high availability of shared storage needs to be considered, and the price is expensive

Images