Master-slave switching method and device for database cluster nodes, equipment and medium

Abstract

The embodiment of the invention discloses a master-slave switching method and device for database cluster nodes, equipment and a medium. The method comprises the steps of determining that a first master node breaks down, wherein the first master node is set to establish master-master synchronization with a second master node, and the first master node is set to establish master-slave synchronization with a first slave node; taking the instance original access address of the first slave node as an instance current access address of the first master node to replace the instance original access address of the first master node; and setting the first slave node and the second master node to establish master-master synchronization, so that an application service continues to access a database according to the name of the first master node. According to the technical scheme, when the cluster node breaks down, the cluster node automatically switches to an available node; transparent master-slave switching access is achieved; and a service user does not perceive switching.

Description

technical field [0001] Embodiments of the present invention relate to database technology, and in particular, to a method, apparatus, device and medium for master-slave switching of database cluster nodes. Background technique [0002] Mysql is a relational database management system that keeps data in different tables instead of putting all the data in one big data warehouse to increase processing speed and increase flexibility. However, the original high availability features of MySQL are not enough to support various accidents in the production environment. For example, after the machine where the Mysql instance is located goes down, this will make the Mysql instance unavailable. In view of this situation, the best solution is to switch the Mysql standby instance to the primary to provide normal services. [0003] In the prior art, Mysql instances are mainly based on the proxy layer or client SDK (Software Development Kit, software development kit) to achieve master-sla...

AI Technical Summary

Problems solved by technology

[0003] In the prior art, the Mysql instance is mainly based on the proxy layer or the client SDK (Software Development Kit, software development kit) to achieve master-slave switching, but there are many shortcomings, for example, the business user needs to manually maintain the access address of the master-slave cluster , switch to other available nodes when the current cluster node is unavailable; when the database proxy layer implements master-slave switching, it is necessary to develop the database proxy layer switching service, which has high development and maintenance costs and large performance loss; the client SDK implements instance intrusion and development during iteration High maintenance costs; when the business side configures the host (Host) solution, it needs to manually replace the local Host file, and the service will not take effect until the Host is restarted, resulting in a long time for master-slave switching, etc.

Images