MySQL database cluster management platform and electronic equipment

Abstract

The embodiment of the invention relates to a MySQL database cluster management platform and electronic equipment. The MySQL database cluster management platform comprises a MySQL specification module, a high-availability module, a host Agent and a domain name resolution module. The MySQL specification module serves as a cluster management and control core and is responsible for carrying out unified arrangement and decision making on full-life-cycle operation of a database cluster and uniformly coordinating other components of the platform to orderly and automatically complete the whole operation according to a set technical process. Cluster management is implemented by using the MySQL database cluster management platform, so that manual operation can be greatly reduced, the management efficiency is improved, and refined and high-reliability management and control of distributed database nodes are achieved.

Description

MySQL database cluster management platform and electronic equipment Technical Field

[0001] This invention relates to the field of cloud-native technology, and in particular to a MySQL database cluster management platform and electronic device. Background Technology

[0002] With the development of the internet and the prevalence of microservice architecture, business data volume has exploded, and the deployment scale and number of MySQL database instances have also expanded rapidly. Daily operation and maintenance management covers several core aspects, including resource provisioning, configuration optimization, data protection, and high availability assurance. Currently, the commonly used traditional operation and maintenance methods rely on a combination of various tools and manual operation, exhibiting significant systemic shortcomings.

[0003] In terms of resource management, the tight coupling between database instances and the underlying server hardware leads to inefficient scaling. Adjusting CPU, memory, or storage specifications usually requires interrupting business services and migrating all data. This process is time-consuming and carries high data migration risks, making it difficult to achieve rapid, elastic responses that are imperceptible to the business side.

[0004] In terms of high availability, tools such as MHA can achieve automatic switching of database master and slave roles, but the IP / domain name mapping update for application access to the database often requires manual intervention, which can lead to service interruptions after failover, forming a breakpoint in the high availability process.

[0005] In terms of daily operation and maintenance, core operations such as cluster creation, backup and recovery, slow query log download, and monitoring and alarm are scattered across different management interfaces or command-line tools. The operation and maintenance process is fragmented and has a low degree of automation, relying heavily on manual operation by operation and maintenance personnel. This not only results in low management efficiency but also makes it easy for database operation risks to occur due to human error. Summary of the Invention

[0006] To address or partially address the aforementioned technical problems, this invention provides a MySQL database cluster management platform and electronic device. It employs a layered collaborative architecture of "MySQL specification module + host agent," where the MySQL specification module serves as the core of cluster management, responsible for unified orchestration and decision-making for the entire lifecycle of the database cluster operations. The host agent, deployed on the cloud hosts of each database node, acts as a local execution agent, receiving decision instructions from the MySQL specification module and automatically executing them, including local operations such as database runtime environment initialization, software deployment, configuration modification, and monitoring data collection. This layered architecture decouples management logic from execution logic, effectively achieving fine-grained and highly reliable management of distributed database nodes.

[0007] In a first aspect, embodiments of the present invention provide a MySQL database cluster management platform. The MySQL database cluster management platform includes:

[0008] The MySQL specification module is used to receive MySQL operation requests, orchestrate the entire lifecycle of the database cluster based on the MySQL operation requests, and generate and issue decision instructions.

[0009] The high availability module is used to monitor the status of each node in the cluster and execute preset switching strategies based on the status of each node or decision instructions.

[0010] The host agent is a cloud host deployed in each database, used to receive and execute corresponding decision instructions;

[0011] The domain name resolution module is used to provide a fixed master database access domain name for the MySQL cluster, and to execute the resolution record to update the master database domain name according to the decision instructions.

[0012] In one implementation, the step of orchestrating the database cluster throughout its entire lifecycle based on MySQL operation requests, and generating and issuing decision instructions, includes:

[0013] Parse MySQL operation requests and perform resource and permission compliance verification based on the parsed operation metadata;

[0014] After successful verification, the database cluster is orchestrated throughout its entire lifecycle based on the operation metadata, decision instructions are generated, and corresponding decision instructions are issued to one or more of the cloud infrastructure, high availability module, host agent, and domain name resolution module.

[0015] In one implementation, the MySQL specification module is further configured to deploy a host agent on the cloud host after the cloud infrastructure completes the creation and configuration of the cloud host according to the decision instructions and returns the basic information of the cloud host. After the host agent completes the deployment and initialization of the MySQL database software and high availability components according to the decision instructions, a decision instruction to execute clustered configuration is issued to the host agent.

[0016] In one implementation, the MySQL specification module is further configured to deploy a host agent on the cloud host after the cloud infrastructure completes the creation and configuration of the new specification cloud host according to the decision instructions and returns the basic information of the cloud host. After the host agent on the cloud host completes the deployment of the MySQL instance and the initialization of the high availability components, master-slave synchronization configuration and data synchronization according to the decision instructions, the high availability module executes the preset switching strategy according to the decision instructions to realize the master-slave switching between the MySQL instance of the old node to be scaled up and the MySQL instance on the cloud host, and the domain name resolution module executes the update of the resolution record of the master database domain name according to the decision instructions, the module issues a decision instruction to the high availability module to remove the cluster association of the old node, an issue to the host agent of the old node to clean up the MySQL instance configuration, and an issue to the cloud infrastructure to execute the destruction of the resources of the old node to be scaled up.

[0017] In one implementation, the MySQL database cluster management platform further includes:

[0018] The front-end module is used to generate MySQL operation requests initiated by users and to display information about the MySQL database cluster.

[0019] In one implementation, the MySQL database cluster management platform further includes:

[0020] The data backup and recovery management module is used to generate backup requests based on backup strategies and send backup requests to the MySQL specification module.

[0021] The MySQL specification module is also used to receive backup requests, generate decision instructions to perform backups based on the backup requests, issue the decision instructions to the target host agent, and after the target host agent completes the backup operation and uploads the backup files to the storage module, it summarizes the metadata of the entire backup process and synchronizes it to the data backup and recovery management module.

[0022] In one implementation, the MySQL database cluster management platform further includes:

[0023] The monitoring and slow query management module is used to collect the running performance indicators of MySQL database instances and the hardware resource indicators of cloud hosts through the host agent. Based on the collected running performance indicators and hardware resource indicators, it monitors the cluster running status in real time and generates and issues alarm information based on predefined alarm rules.

[0024] In one implementation, the monitoring and slow query management module is further used to collect slow query logs through the host agent, and to store and analyze the log data.

[0025] Secondly, embodiments of the present invention provide an electronic device, the electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the functions of the aforementioned MySQL database cluster management platform.

[0026] In this embodiment of the invention, the MySQL specification module serves as the core of cluster management, responsible for the unified orchestration and decision-making of the entire lifecycle operations of the database cluster, and coordinating other components of the platform to complete the entire operation in an orderly and automated manner according to predetermined technical processes. Utilizing the aforementioned MySQL database cluster management platform for cluster management can significantly reduce manual operations, improve management efficiency, and achieve refined and highly reliable control over distributed database nodes. Attached Figure Description

[0027] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 is a schematic diagram of the structure of the MySQL database cluster management platform provided in an embodiment of the present invention;

[0029] Figure 2 is a schematic diagram of the structure of the electronic device provided in an embodiment of the present invention. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0031] The MySQL database cluster management platform provided in this invention adopts a layered collaborative architecture of "MySQL specification module + host agent". The MySQL specification module serves as the core of cluster management, responsible for unified orchestration and decision-making for the entire lifecycle of the database cluster operations, and coordinating other components of the platform to complete the entire operation in an orderly and automated manner according to predetermined technical processes. The host agent, deployed on the cloud hosts of each database node, acts as a local execution agent, receiving decision instructions from the MySQL specification module and automatically executing them, including local operations such as database runtime environment initialization, software deployment, configuration modification, and monitoring data collection. This layered architecture decouples the management logic from the execution logic, effectively achieving fine-grained and highly reliable management of distributed database nodes.

[0032] Specifically, referring to Figure 1, which is a structural schematic diagram of the MySQL database cluster management platform provided in an embodiment of the present invention, the MySQL database cluster management platform provided in an embodiment of the present invention includes:

[0033] MySQL specification module 10 is used to receive MySQL operation requests, orchestrate the database cluster throughout its entire lifecycle based on the MySQL operation requests, and generate and issue decision instructions.

[0034] High availability module 11 is used to monitor the status of each node in the cluster and execute preset switching strategies based on the status of each node or decision instructions.

[0035] Host Agent 12 is a cloud host deployed in each database, used to receive and execute corresponding decision instructions;

[0036] Domain name resolution module 13 is used to provide a fixed master database access domain name for the MySQL cluster, and to execute the resolution record to update the master database domain name according to the decision instruction.

[0037] All MySQL operation requests initiated by users in the front end (such as front end modules, API interfaces, command line tools, etc.), such as cluster creation and destruction, node scaling, cluster / instance configuration management, data backup and recovery, etc., will be uniformly sent to the MySQL specification module. After receiving a MySQL operation request, the MySQL specification module first parses the request to obtain operation metadata, such as basic request identifier data (e.g., globally unique request ID, initiator information), core operation metadata (e.g., core operation actions, operation execution priority, operation scope), resource target metadata (e.g., target cluster information, target node / instance information), and configuration rule metadata (e.g., resource configuration information, configuration modification information). Then, based on the parsed operation metadata, it performs resource and permission compliance verification to check whether user permissions, resources are sufficient, and request parameters are compliant. After the verification is passed, it orchestrates the entire lifecycle of the database cluster according to the operation metadata, generates decision instructions, and issues corresponding decision instructions to one or more of the cloud infrastructure, high availability module, host agent, and domain name resolution module to coordinate the cloud infrastructure and other components of the platform to complete the entire operation in an orderly and automatic manner according to the established technical process.

[0038] The aforementioned full lifecycle refers to all management stages of MySQL from creation to destruction, including all operations such as creation, configuration, scaling up / down, failover, parameter modification, backup and recovery, and destruction.

[0039] The process for creating a database provided in this embodiment of the invention may include:

[0040] 1) Users submit MySQL operation requests for cluster creation through the front end. These MySQL operation requests contain operation metadata such as specifications, architecture, and number of nodes.

[0041] 2) After receiving a MySQL operation request, the MySQL specification module parses the MySQL operation request, performs resource and permission compliance verification based on the parsed operation metadata, and after the verification is passed, orchestrates the database cluster for the entire lifecycle according to the operation metadata, and generates and issues decision instructions.

[0042] 3) After receiving the corresponding decision instructions, the cloud infrastructure completes the creation and configuration of the cloud host according to the decision instructions, and returns the basic information of the cloud host (including the list of IP addresses) to the MySQL specification module.

[0043] 4) The MySQL specification module deploys the host agent on the cloud host, and then issues decision instructions to the host agent to execute the deployment and initialization of the MySQL database software and high availability components. After the deployment and initialization of the MySQL database software and high availability components are completed, it issues decision instructions to the host agent to execute the clustering configuration.

[0044] 5) The host agent executes the master-slave replication configuration according to the decision instructions, establishes the master-slave synchronization relationship, and after the cluster is built, feeds back the cluster ready status information to the MySQL specification module.

[0045] The above process achieves a fully automated workflow from virtual machine resource (cloud host) application to database cluster delivery.

[0046] The database scaling process provided in this embodiment of the invention may include:

[0047] 1) Users submit MySQL operation requests for scaling up or down the database through the front end. When the MySQL operation request is for vertical scaling up or down, it can include operation metadata such as single-node CPU / memory / storage hardware.

[0048] 2) After receiving a MySQL operation request, the MySQL specification module parses the MySQL operation request, performs resource and permission compliance verification based on the parsed operation metadata, and after the verification is passed, orchestrates the database cluster for the entire lifecycle according to the operation metadata, and generates and issues decision instructions.

[0049] 3) After receiving the corresponding decision instructions, the cloud infrastructure completes the creation and configuration of the new specification cloud host according to the decision instructions, and returns the basic information of the cloud host;

[0050] 4) The MySQL specification module deploys a host agent on the cloud host, and then issues a decision instruction to the host agent on the cloud host to execute the MySQL instance deployment and high availability component initialization. After the MySQL instance deployment and high availability component initialization are completed, it issues a decision instruction to the host agent on the cloud host to execute master-slave synchronization configuration and data synchronization, an order to the old node host agent to execute backup file push, and an order to the high availability module to execute master-slave synchronization status monitoring and verification.

[0051] 5) After receiving the decision instruction, the old node host Agent performs local operations, including enabling binlog persistence, creating a dedicated authorized account for master-slave synchronization, opening the synchronization port, generating a full data backup file, and pushing the backup file to the specified storage directory of the new specification cloud host.

[0052] After receiving the decision command, the host agent (new node host agent) on the cloud host obtains the synchronization information of the old node, loads the full data backup file pushed by the old node, and completes the full data recovery of the new node MySQL instance; configures the master-slave synchronization parameters of the new node MySQL instance, starts the IO / SQL thread, pulls the binlog logs of the old master node, and performs incremental data synchronization; during the synchronization process, the master-slave synchronization status of the new node is collected in real time and reported to the high availability module.

[0053] The high availability module continuously monitors the synchronization status of new and old nodes until the verification criteria are met, such as full data recovery completed + incremental synchronization without delay + GTID matching. Once the synchronization is confirmed, the synchronization result is fed back to the MySQL specification module.

[0054] 6) The high availability module executes the preset switching strategy according to the decision instructions to realize the master-slave switching between the MySQL instance of the old node to be scaled up and the MySQL instance on the cloud host. After the master-slave switching is completed and the status verification of the new master node is passed, the feedback is sent to the MySQL specification module.

[0055] 7) The MySQL specification module sends a decision instruction to the domain name resolution module to update the DNS resolution record of the master database domain name. The domain name resolution module updates the DNS resolution record of the master database domain name, seamlessly redirecting business traffic from the old master node to the new master node. After completing the full-dimensional status verification of the new node and ensuring that the old node has no business request connections, the verification result is fed back to the MySQL specification module.

[0056] 8) The MySQL specification module sends a decision instruction to the high availability module to disconnect the old node from the cluster. After receiving the decision instruction, the high availability module completes the decoupling of the old node at the cluster level.

[0057] Subsequently, the MySQL specification module sends a decision instruction to the host agent of the old node to clean up the MySQL instance configuration corresponding to the old node. After receiving the decision instruction, the host agent of the old node performs a local configuration cleanup operation, completely deleting all configurations, records, and files related to MySQL / cluster.

[0058] After the MySQL specification module verifies and cleans up the results, it sends a decision instruction to the cloud infrastructure to execute the destruction of resources of the old nodes to be scaled up or down. After receiving the decision instruction from the cloud infrastructure, it executes the underlying virtualization resource reclamation operation of the old nodes.

[0059] The above process achieves a fully automated workflow for scaling up and down the database, enabling seamless elastic scaling for business operations.

[0060] In this embodiment, the MySQL database cluster management platform may further include:

[0061] Front-end module 14 is used to generate MySQL operation requests initiated by users and to display information about the MySQL database cluster;

[0062] The data backup and recovery management module 15 is used to generate backup requests according to the backup strategy and send backup requests to the MySQL specification module;

[0063] The monitoring and slow query management module 16 is used to collect the running performance indicators of MySQL database instances and the hardware resource indicators of cloud hosts through the host agent, monitor the cluster running status in real time based on the collected running performance indicators and hardware resource indicators, and generate and issue alarm information based on predefined alarm rules; and to collect slow query logs through the host agent, store and analyze log data.

[0064] Specifically, the front-end module provides users with a graphical user interface, standardized request configuration forms, and operation process guidance. It supports users in initiating a full range of MySQL-related operation requests, including cluster creation, scaling up / down, master-slave switching, backup and recovery, parameter modification, and resource reclamation. Users can complete operations such as selecting operation objects, setting configuration parameters, and confirming execution constraints within the interface. The front-end module encapsulates the user-configured information into structured MySQL operation requests according to platform specifications.

[0065] The front-end module can also receive cluster information pushed by the MySQL specification module, high availability module, monitoring and slow query management module, and data backup and recovery management module in real time. Through dashboards, lists, charts and other visualization forms, it can display information of the MySQL database cluster to users (cluster ID / name, deployment region, number of nodes), node status (roles, resource specifications, running status of each node), instance running indicators (QPS / TPS, number of connections, master-slave synchronization latency, disk utilization), operation execution records (request ID, operation type, execution status, execution time, result), alarm information (alarm level, alarm content, triggering node, processing status), backup information (backup file list, status information), etc. It supports users to perform multi-dimensional queries, filtering and detailed viewing of cluster information, realizing real-time monitoring of cluster running status and traceability of the entire operation process.

[0066] As the core module for ensuring data security in a MySQL database cluster, the data backup and recovery management module can receive various backup strategies configured by users through the front-end module, store and parse the backup strategies, automatically and standardizedly generate backup requests according to preset rules based on the parsed backup strategies, and push the backup requests to the MySQL specification module.

[0067] The MySQL specification module is also used to receive backup requests, generate decision instructions to perform backups based on the backup requests, issue the decision instructions to the target host agent, and after the target host agent completes the backup operation and uploads the backup files to the storage module, it summarizes the metadata of the entire backup process and synchronizes it to the data backup and recovery management module.

[0068] Specifically, after receiving a backup request from the data backup and recovery management module, the MySQL specification module first parses the backup request and verifies its permission compliance. After the verification is successful, it generates standardized decision instructions based on the parsed parameters and sends them to the host agent of the target cloud host. After the host agent completes the backup data collection, backup file generation, and backup file upload to the storage module on the target cloud host, it summarizes the metadata of the entire backup process (including backup file storage path, size, checksum, execution status, etc.) and synchronizes it to the data backup and recovery management module. Then, the data backup and recovery management module pushes the metadata information to the front-end module for display.

[0069] In this embodiment, the MySQL specification module serves as the core of cluster management, responsible for the unified orchestration and decision-making of the entire lifecycle operations of the database cluster, and coordinating other components of the platform to complete the entire operation in an orderly and automated manner according to predetermined technical processes. Utilizing the MySQL database cluster management platform for cluster management can significantly reduce manual operations, improve management efficiency, and achieve refined and highly reliable control over distributed database nodes.

[0070] Figure 2 illustrates a schematic diagram of an electronic device 20 that can be used to implement embodiments of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0071] As shown in Figure 2, the electronic device 20 includes at least one processor 21 and a memory, such as a read-only memory (ROM) 32 and a random access memory (RAM) 23, communicatively connected to the at least one processor 21. The memory stores computer programs executable by the at least one processor. The processor 21 can perform various appropriate actions and processes based on the computer program stored in the ROM 32 or loaded from storage unit 28 into the RAM 23. The RAM 23 can also store various programs and data required for the operation of the electronic device 20. The processor 21, ROM 32, and RAM 23 are interconnected via a bus 24. An input / output (I / O) interface 25 is also connected to the bus 24.

[0072] Multiple components in electronic device 20 are connected to I / O interface 25, including: input unit 26, such as keyboard, mouse, etc.; output unit 27, such as various types of monitors, speakers, etc.; storage unit 28, such as disk, optical disk, etc.; and communication unit 29, such as network card, modem, wireless transceiver, etc. Communication unit 29 allows electronic device 20 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0073] Processor 21 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 21 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. When processor 21 executes the computer program, it implements the functionality of the MySQL database cluster management platform described above.

[0074] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0075] To provide interaction with the user, the functions and techniques of the management platform described herein can be implemented on an electronic device having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0076] The functionalities and technologies of the management platform described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with the implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0077] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0078] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0079] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A MySQL database cluster management platform, characterized in that, include: The MySQL specification module is used to receive MySQL operation requests, orchestrate the entire lifecycle of the database cluster based on the MySQL operation requests, and generate and issue decision instructions. The high availability module is used to monitor the status of each node in the cluster and execute preset switching strategies based on the status of each node or decision instructions; the host agent is a cloud host deployed in each database to receive and execute corresponding decision instructions. The domain name resolution module is used to provide a fixed master database access domain name for the MySQL cluster, and to execute the resolution record to update the master database domain name according to the decision instructions.

2. The MySQL database cluster management platform according to claim 1, characterized in that, The process of orchestrating the database cluster throughout its entire lifecycle based on MySQL operation requests, and generating and issuing decision instructions, includes: parsing the MySQL operation requests, performing resource and permission compliance verification based on the parsed operation metadata; after the verification is passed, orchestrating the database cluster throughout its entire lifecycle based on the operation metadata, generating decision instructions, and issuing corresponding decision instructions to one or more of the cloud infrastructure, high availability module, host agent, and domain name resolution module.

3. The MySQL database cluster management platform according to claim 2, characterized in that: The MySQL specification module is also used to deploy a host agent on the cloud host after the cloud infrastructure completes the creation and configuration of the cloud host according to the decision instructions and returns the basic information of the cloud host. After the host agent completes the deployment and initialization of the MySQL database software and high availability components according to the decision instructions, a decision instruction to execute the cluster configuration is issued to the host agent.

4. The MySQL database cluster management platform according to claim 2, characterized in that: The MySQL specification module is also used to deploy a host agent on the cloud host after the cloud infrastructure completes the creation and configuration of the new specification cloud host according to the decision instructions and returns the basic information of the cloud host. After the host agent on the cloud host completes the deployment of the MySQL instance and the initialization of the high availability components, master-slave synchronization configuration and data synchronization according to the decision instructions, the high availability module executes the preset switching strategy according to the decision instructions to realize the master-slave switching between the MySQL instance of the old node to be scaled up and the MySQL instance on the cloud host, and the domain name resolution module executes the update of the resolution record of the master database domain name according to the decision instructions, it issues a decision instruction to the high availability module to remove the cluster association of the old node, an issue to the host agent of the old node to clean up the MySQL instance configuration, and an issue to the cloud infrastructure to execute the destruction of the resources of the old node to be scaled up.

5. The MySQL database cluster management platform according to any one of claims 1 to 4, characterized in that, Also includes: The front-end module is used to generate MySQL operation requests initiated by users and to display information about the MySQL database cluster.

6. The MySQL database cluster management platform according to claim 5, characterized in that, Also includes: The data backup and recovery management module is used to generate backup requests based on backup strategies and send backup requests to the MySQL specification module. The MySQL specification module is also used to receive backup requests, generate decision instructions to perform backups based on the backup requests, issue the decision instructions to the target host agent, and after the target host agent completes the backup operation and uploads the backup files to the storage module, it summarizes the metadata of the entire backup process and synchronizes it to the data backup and recovery management module.

7. The MySQL database cluster management platform according to claim 5, characterized in that, Also includes: The monitoring and slow query management module is used to collect the running performance indicators of MySQL database instances and the hardware resource indicators of cloud hosts through the host agent. Based on the collected running performance indicators and hardware resource indicators, it monitors the cluster running status in real time and generates and issues alarm information based on predefined alarm rules.

8. The MySQL database cluster management platform according to claim 7, characterized in that, The monitoring and slow query management module is also used to collect slow query logs through the host agent, and to store and analyze the log data.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the functions of the MySQL database cluster management platform as described in any one of claims 1 to 8.

Images