A switching control method, device and equipment of a cloud platform management node

Abstract

The embodiment of the present application provides a kind of cloud platform management node switching control method, device and equipment, the method comprises: obtaining the state data of cloud platform management main node;When the state data is failure, select new cloud platform management main node from at least two groups of cloud platform management backup nodes;The virtual IP address of original cloud platform management main node is bound with new cloud platform management main node, and routing redirection is completed;Control the task of original cloud platform management main node switches to the new cloud platform management main node processing;And control the cloud platform management main node and cloud platform management backup node keep data synchronization.The embodiment of the present application selects new main node from at least two groups of backup nodes, ensures that the selected new main node is in normal state and has enough resources, avoids new problem after switching.

Description

Technical Field

[0001] This invention relates to the field of cloud computing technology, and in particular to a method, apparatus, and device for switching control of cloud platform management nodes. Background Technology

[0002] To effectively manage cloud platform computing resources, a unified management node is typically deployed within the cloud platform to handle tasks such as task scheduling, resource allocation, virtual machine status monitoring, and configuration management. Currently, the cloud platform management master node is generally deployed as a single point or uses manual master-slave failover. If the cloud platform management master node fails, the cloud platform cannot promptly perform core functions such as task scheduling and virtual machine control. Furthermore, the status of the cloud platform management backup node is not monitored, leading to issues such as the backup node still experiencing failures or insufficient resources after failover. Summary of the Invention

[0003] The technical problem to be solved by the embodiments of the present invention is to provide a switching control method, apparatus and device for cloud platform management nodes, which selects a new master node from at least two sets of backup nodes, ensures that the selected new master node is in a normal state and has sufficient resources, and avoids new problems after switching.

[0004] To solve the above-mentioned technical problems, the technical solution of the present invention is as follows: A method for controlling the switching of cloud platform management nodes, comprising: Obtain the status data of the cloud platform management master node; When the status data indicates a fault, a new cloud platform management master node is selected from at least two sets of cloud platform management backup nodes; Bind the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and complete the route redirection; The task of the original cloud platform management master node is switched to the new cloud platform management master node for processing; and the cloud platform management master node and the cloud platform management backup node are kept in data synchronization.

[0005] Optionally, the status data is a response signal from the cloud platform management master node to the detection signals periodically sent by the cloud platform management backup node.

[0006] Optionally, when the status data indicates a fault, a new cloud platform management master node is selected from at least two groups of cloud platform management backup nodes, including: If the status data shows multiple consecutive unresponsive events, the cloud platform management master node is determined to be faulty. Control all cloud platform management backup nodes to enter election status and start the master node election process; Once successfully selected, the winning cloud platform management backup node becomes the new cloud platform management master node.

[0007] Optionally, control all cloud platform management backup nodes to enter election mode and initiate the master node election process, including: Control all cloud platform management backup nodes to suspend providing data processing services to the outside world, and retain only the communication functions related to the election; Perform qualification verification on each cloud platform management backup node; according to Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E Determine the priority score of each cloud platform's management backup node; in, Z Priority scores are assigned to backup nodes managed by the cloud platform. A To preset the basic level, B For the health of hardware resources, C To ensure the success rate of historical takeovers, D Due to data synchronization delay, E For network connection stability, p 1 As the first weight, p 2 As the second weight, p 3 As the third weight, p 4 As the fourth weight, p 5 It is the fifth weight; The cloud platform management backup node with the highest priority score will be designated as the new cloud platform management master node.

[0008] Optionally, the methods for determining the hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability include: according to B=Y- ( p 6 × B 1 +p 7 × B 2+p 8 × B 3 This involves determining the health of hardware resources for each cloud platform's management backup nodes. in, B To manage the hardware resource health of backup nodes for cloud platforms. Y This represents the highest possible value for hardware resource health. B 1 For CPU utilization, B 2 For memory usage, B 3 Disk I / O load rate, p 6 It is the sixth weight. p 7 It is the seventh weight. p 8 It is the eighth weight; according to C=C 1 / C 2 Determine the historical takeover success rate of each cloud platform's management backup nodes; in, C To improve the historical takeover success rate of backup nodes managed by the cloud platform, C 1 For the number of successful takeovers, C 2 Number of takeover attempts; according to D=1÷ ( 1+D 1 ), determine the data synchronization delay of each cloud platform management backup node; in, D To manage data synchronization latency of backup nodes on the cloud platform, D 1 The average delay in seconds; according to E= ( p 9 × E 1 +p 10 × E 2 ), determine the network connection stability of each cloud platform management backup node; in, E To ensure the stability of network connectivity for backup nodes managed by the cloud platform, E 1 For network connectivity, E 2 For packet loss rate, p9 It is the ninth weight. p 10 It is the tenth weight.

[0009] Optionally, the virtual IP address of the original cloud platform management master node is bound to the new cloud platform management master node, and route redirection is completed, including: unbinding the original cloud platform management master node from the virtual IP address; Bind the virtual IP address to the network interface of the new cloud platform management master node; The address mapping update notification is sent to all devices in the network via Address Resolution Protocol (ARP) broadcast, thus completing the route redirection.

[0010] Optionally, controlling the task switching from the original cloud platform management master node to the new cloud platform management master node includes: Control the new cloud platform management master node to obtain tasks synchronized from the original cloud platform management master node; Control the new cloud platform management master node to process the tasks of the original cloud platform management master node.

[0011] Embodiments of the present invention also provide a switching control device for a cloud platform management node, comprising: The acquisition module is used to acquire status data of the cloud platform management master node; The processing module is used to select a new cloud platform management master node from at least two sets of cloud platform management backup nodes when the status data is faulty; bind the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and complete the route redirection; control the task of the original cloud platform management master node to be switched to the new cloud platform management master node for processing; and control the cloud platform management master node to keep the data synchronized with the cloud platform management backup node.

[0012] Embodiments of the present invention also provide a computing device, comprising: One or more processors; A storage device for storing one or more programs that, when executed by one or more processors, cause the one or more processors to perform the method as described above.

[0013] Embodiments of the present invention also provide a computing device readable storage medium storing a program that, when executed by a processor, implements the method described above.

[0014] The above-described solutions of the embodiments of the present invention have at least the following beneficial effects: The above-described solution of this invention automatically detects the status of the master node and automatically selects a new master node from the backup nodes when the master node fails, without the need for manual intervention, which greatly shortens the fault recovery time and ensures the continuous operation of the core functions of the cloud platform.

[0015] By binding virtual IP addresses and redirecting routes, the new master node seamlessly takes over the network identity of the original master node, and external requests can be automatically routed to the new master node without modifying the configuration. At the same time, the new master node directly processes the tasks of the original master node, and combined with the data synchronization mechanism of the master and backup nodes, it ensures that tasks are not lost and services are not interrupted.

[0016] A new primary node is selected from at least two sets of backup nodes, ensuring that the selected primary node is in a normal state and has sufficient resources to avoid new problems after the switchover and improve the reliability of the switchover. This application verifies the qualifications of the backup nodes managed by each cloud platform by determining the hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability, which greatly improves the accuracy and efficiency of hardware operation.

[0017] The primary and backup node data synchronization mechanism ensures that the backup node updates the primary node's data in real time, avoiding data discrepancies. Attached Figure Description

[0018] Figure 1 This is a flowchart of a cloud platform management node switching control method according to an embodiment of the present invention.

[0019] Figure 2 This is a schematic diagram of the components of the switching control system for the cloud platform management node in an embodiment of the present invention.

[0020] Figure 3 This is a schematic diagram of the specific structure of the cloud platform management node switching control system according to an embodiment of the present invention.

[0021] Figure 4 This is a flowchart illustrating the switching control process of the cloud platform management node according to an embodiment of the present invention.

[0022] Figure 5 This is a schematic diagram of the overall structure of the cloud platform management node switching control system according to an embodiment of the present invention.

[0023] Figure 6 This is a schematic diagram of the switching control device for the cloud platform management node according to an embodiment of the present invention. Detailed Implementation

[0024] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0025] like Figure 1 As shown, an embodiment of the present invention provides a switching control method for a cloud platform management node, including: Step 11: Obtain the status data of the cloud platform management master node; Step 12: When the status data indicates a fault, select a new cloud platform management master node from at least two sets of cloud platform management backup nodes; Step 13: Bind the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and complete the route redirection; specifically, the virtual IP address is an Internet Protocol address; Step 14: Control the task of the original cloud platform management master node to be switched to the new cloud platform management master node for processing; and control the cloud platform management master node to keep data synchronized with the cloud platform management backup node.

[0026] In this embodiment, by automatically detecting the status of the master node, a new master node is automatically selected from the backup nodes when the master node fails, without the need for manual intervention, which greatly shortens the fault recovery time and ensures the continuous operation of the core functions of the cloud platform.

[0027] By binding virtual IP addresses and redirecting routes, the new master node can seamlessly take over the network identity of the original master node. External requests can be automatically routed to the new master node without modifying the configuration. At the same time, the new master node directly processes the tasks of the original master node. Combined with the data synchronization mechanism of the master and backup nodes, it ensures that tasks are not lost and services are not interrupted.

[0028] A new primary node is selected from at least two sets of backup nodes, ensuring that the selected primary node is in a normal state and has sufficient resources to avoid new problems after the switchover and improve the reliability of the switchover. This application verifies the qualifications of the backup nodes managed by each cloud platform by determining the hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability, which greatly improves the accuracy and efficiency of hardware operation.

[0029] The primary and backup node data synchronization mechanism ensures that the backup node updates the primary node's data in real time, avoiding data discrepancies.

[0030] In an optional embodiment of the present invention, in step 11, the status data is a response signal of the cloud platform management master node to the detection signal periodically sent by the cloud platform management backup node.

[0031] Specifically, the cloud platform management backup node generates a standardized detection signal according to a preset cycle. The detection signal includes a timestamp, backup node identifier, random check code, and the sequence number of this detection. The detection signal is sent to the cloud platform management master node through a dedicated communication link within the cluster. After receiving the detection signal, the cloud platform management master node immediately verifies the validity of the random check code and generates a response signal within a fixed time limit. The response signal includes the master node identifier, confirmation information corresponding to the current detection sequence number, the running status of the master node's current core process, and a snapshot of the critical resource utilization rate. The response signal is then sent back to the cloud platform management backup node that sent the detection signal. The system obtains the response signal.

[0032] In this embodiment, the detection signal contains a random check code, which can effectively prevent the signal from being tampered with or forged during transmission, ensuring that the master node receives a genuine and valid detection request.

[0033] Setting a fixed response time limit (e.g., within 100ms) ensures that the response status of the master node can be accurately timed, providing a clear basis for determining faults caused by continuous non-response.

[0034] In an optional embodiment of the present invention, in step 12, when the status data indicates a fault, selecting a new cloud platform management master node from at least two groups of cloud platform management backup nodes includes: Step 121: When the status data shows multiple consecutive (e.g., 3 times) no response (or multiple consecutive times the critical resource occupancy rate exceeds the preset threshold), the cloud platform management master node is determined to be faulty. Step 122: Control all cloud platform management backup nodes to enter election state and start the master node election process; Step 123: After successful selection, the winning cloud platform management backup node becomes the new cloud platform management master node.

[0035] In this embodiment, multiple consecutive unresponsive events or multiple consecutive critical resource exceedances are explicitly used as fault determination conditions, rather than triggering a switchover based on a single anomaly. This effectively filters out non-fatal issues such as network jitter and temporary resource spikes, reduces cluster instability caused by misjudgment, and ensures the stability of system operation.

[0036] All backup nodes are required to enter the election state and start a standardized process to avoid conflicts caused by multiple nodes vying for the master node role in an disorderly manner.

[0037] Even if some backup nodes are abnormal, the best one can still be selected from the remaining nodes, further improving the cluster's resilience.

[0038] In an optional embodiment of the present invention, step 122, controlling all cloud platform management backup nodes to enter the election state and initiating the master node election process, includes: Step 1221: Control all cloud platform management backup nodes to suspend providing data processing services to the outside world, and only retain communication functions related to the election; Step 1222: Verify the eligibility of each cloud platform management backup node; Step 1223, according to Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E Determine the priority score of each cloud platform's management backup node; in, Z Priority scores are assigned to backup nodes managed by the cloud platform. A To preset the basic level, B For the health of hardware resources, C To ensure the success rate of historical takeovers, D Due to data synchronization delay, E For network connection stability, p 1 As the first weight, p 2 As the second weight, p 3 As the third weight, p 4 As the fourth weight, p 5 It is the fifth weight; The cloud platform management backup node with the highest priority score will be designated as the new cloud platform management master node.

[0039] In this embodiment, by suspending external data processing services and retaining election communication functions, all backup nodes are temporarily removed from regular business loads, avoiding resource contention caused by parallel processing tasks (such as excessive CPU / memory usage affecting election signal transmission), ensuring that nodes concentrate their computing power on election-related information interaction and calculation, and reducing the risk of process interruption.

[0040] The qualification verification mechanism (such as verifying data synchronization integrity, hardware health, network connectivity, etc.) can eliminate backup nodes that do not meet the operating requirements of the master node in advance (such as nodes with excessive data synchronization delays or potential hardware failures), thus ensuring the quality of the candidate pool from the source.

[0041] Priority calculation formula ( Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E This approach quantifies and integrates key factors affecting master node competence (preset base level, hardware health, historical performance, data synchronization quality, and network stability), and reflects the importance of each factor through weight allocation. This method avoids biases caused by relying on a single indicator (such as looking only at hardware performance) or subjective judgment, making priority ranking more objective and interpretable.

[0042] By prioritizing the node with the highest score, the final decision-making process is simplified, avoiding excessively long selection times caused by complex negotiations. Combined with pre-screening through qualification verification, all nodes participating in the scoring are qualified candidates, further ensuring the comprehensive advantages of the highest-scoring node in terms of hardware, data, and network. This enables it to quickly take over the functions of the master node, shortening the interval between the failure of the original master node and the online launch of the new master node, and reducing the impact of business interruption.

[0043] In an optional embodiment of the present invention, the determination of hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability in step 1223 includes: Step 12231, according to B=Y- ( p 6 × B 1 +p 7 × B 2 +p 8 × B 3 This involves determining the health of hardware resources for each cloud platform's management backup nodes. in, B To manage the hardware resource health of backup nodes for cloud platforms.Y This represents the highest possible value for hardware resource health. B 1 For CPU utilization, B 2 For memory usage, B 3 Disk I / O load rate, p 6 It is the sixth weight. p 7 It is the seventh weight. p 8 It is the eighth weight; Step 12232, according to C=C 1 / C 2 Determine the historical takeover success rate of each cloud platform management backup node; determine the historical takeover success rate of cloud platform management backup nodes participating in the election for the first time. C To preset the success rate C 3 ; in, C To improve the historical takeover success rate of backup nodes managed by the cloud platform, C 1 For the number of successful takeovers, C 2 Number of takeover attempts; Step 12233, according to D=1÷ ( 1+D 1 ), determine the data synchronization delay of each cloud platform management backup node; in, D To manage data synchronization latency of backup nodes on the cloud platform, D 1 The average delay in seconds; Steps 12234, according to E= ( p 9 × E 1 +p 10 × E 2 ), determine the network connection stability of each cloud platform management backup node; in, E To ensure the stability of network connectivity for backup nodes managed by the cloud platform, E 1 For network connectivity, E 2 For packet loss rate, p 9 It is the ninth weight. p10 It is the tenth weight.

[0044] In this embodiment, the hardware resource health calculation accurately reflects the node redundancy capability by subtracting the resource usage weighted sum from the highest value, eliminating the impact of hardware differences and ensuring fair evaluation.

[0045] The historical takeover success rate calculation is set as a preset value for new nodes to solve the problem of no historical data, balance experience and fairness, and enhance the inclusiveness of the mechanism.

[0046] The data synchronization delay is converted using a reciprocal to amplify the advantages of low-latency nodes, quickly identify data risk nodes, and ensure service continuity.

[0047] The network connection stability formula integrates connectivity rate and packet loss rate to comprehensively evaluate communication quality and reduce scheduling delays and data loss.

[0048] In an optional embodiment of the present invention, step 13, which involves binding the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and completing route redirection, includes: Step 131: Unbind the original cloud platform management master node from the virtual IP address; Step 132: Bind the virtual IP address to the network interface of the new cloud platform management master node; Step 133: Send an address mapping update notification to all devices in the network via Address Resolution Protocol (ARP) broadcast to complete the route redirection.

[0049] In this embodiment, step 131 actively unbinds the original master node from the virtual IP to avoid address conflicts caused by the original node still occupying the virtual IP after failure; step 132 binds the virtual IP to the new master node to ensure the unique pointing of the network identifier.

[0050] Step 133 forces an address mapping update via ARP broadcast, directly notifying all devices in the network (such as switches, routers, and other nodes).

[0051] Unbinding, binding, and broadcasting updates form a complete closed loop for virtual IP migration, fundamentally avoiding problems such as address conflicts and routing chaos, and ensuring the accuracy and stability of network communication after the new master node takes over.

[0052] In an optional embodiment of the present invention, step 14, controlling the task switching of the original cloud platform management master node to the new cloud platform management master node, includes: Step 141: Control the new cloud platform management master node to obtain tasks synchronized from the original cloud platform management master node; Step 142: Control the new cloud platform management master node to process the tasks of the original cloud platform management master node.

[0053] Specifically, the new cloud platform management master node receives synchronization data sent by the original master node through data synchronization. This data includes key information such as task execution records, virtual machine running status and configuration information, and resource usage. Data synchronization employs a multicast communication mechanism to ensure that the new master node can efficiently and reliably acquire the data related to the aforementioned tasks, thereby guaranteeing data integrity and consistency. The new master node parses and verifies the acquired synchronization data to confirm that the data has not been damaged or lost, thus providing a reliable data foundation for subsequent task processing. The new master node judges the status of the tasks synchronized from the original master node to determine whether the task is in execution, has not started, or has been interrupted. If there are any unfinished tasks, the new master node will continue to execute these tasks according to the task information record, priority, and scheduling logic. For example, for an ongoing virtual machine migration task, the new master node will take over the migration process and complete subsequent operations such as target virtual machine routing and resource allocation, and backup of critical data and network information to ensure the task is completed smoothly. If an anomaly is detected in a task, such as a task failure due to a fault in the original master node, the new master node will trigger a retry mechanism according to a preset strategy to reschedule resources to execute the task. At the same time, this will prevent the task from being executed repeatedly and ensure the rational use of system resources. When a critical virtual machine-related task is detected, the new master node will prioritize its processing. If the critical virtual machine is in an abnormal state (such as crashing or resource exhaustion), the migration task will be triggered immediately through the task scheduling module, and the migration module will perform the migration operation to ensure the continuous operation of critical services. During the task processing, the new master node will monitor the host machine's resource status in real time, allocate resources reasonably, and avoid resource conflicts and waste.

[0054] In this embodiment, relying on the data synchronization mechanism, the new master node efficiently obtains complete task data, which is verified to ensure reliability, avoids task loss or state confusion, and ensures business continuity.

[0055] The new master node determines the task status, continues unfinished tasks according to priority, triggers retries for abnormal tasks, avoids repeated execution, and achieves seamless takeover.

[0056] Prioritize critical virtual machine tasks, quickly trigger migration in case of anomalies, ensure the stability of core businesses, and enhance the risk resistance of high-priority businesses.

[0057] Real-time monitoring of host machine resources, reasonable allocation to avoid conflicts, and integration with a unified control module to ensure single-node activation, thereby optimizing resource utilization and system stability.

[0058] In the above embodiments of the present invention, automatic primary / backup failover can be performed when the primary node fails, ensuring the continuous operation of critical functions. A diagram of the virtual IP failover component is attached. Figure 2 , 3 As shown. The software module structure mainly includes the following functional modules: Virtual IP Failover Manager: This module is responsible for selecting the host and automatically binding virtual IPs. After the host starts up, a master node is selected through a master-slave contention mechanism, and the virtual IP is bound to its network interface. The unified control module is then notified to activate the current host to take over the following functions: data acquisition, task scheduling, virtual machine migration, etc. Through the binding and switching of virtual IPs, business access is made seamless regardless of changes in the master node.

[0059] Unified Control Module: In a high-availability cluster environment, to avoid resource waste, duplicate consumption, or system pressure caused by multiple nodes simultaneously performing data collection, task execution, etc., this module is responsible for managing the status of active nodes in the cluster. Its core function is to ensure that only one master node is active at any given time, with the rest being hot standby nodes, thus achieving single scheduling of tasks and data consistency in a high-availability environment.

[0060] Host Management Module: This module is responsible for managing all host resources on the cloud platform. Its main functions include: setting host access parameters (IP, port, authorization code); and enabling host registration, querying, and status monitoring.

[0061] After the host machine information is configured, the system can collect the running status of the virtual machines on it through the cloud server cryptographic machine management interface, so as to achieve standardized and unified resource access and management.

[0062] Data Acquisition Module: This module is responsible for collecting the following virtualization resource information from each host machine: The data collected, including basic virtual machine information (such as name and UUID), virtual machine running status (running, shut down, suspended), and resource usage (CPU usage, memory usage, etc.), will serve as the basic support for task scheduling and help determine the availability and resource health of the virtual machine.

[0063] Task scheduling module: Based on the information provided by the data acquisition module, it performs logical analysis to determine whether the virtual machine is in an abnormal state (such as crash or resource exhaustion). Once an anomaly is detected, it immediately triggers a migration task and submits it to the migration module for execution, ensuring uninterrupted high availability of services.

[0064] Migration Module: Responsible for executing virtual machine migration operations. Core functions include: migration task logging (recording the execution status of migration tasks, target host machine, etc.); target virtual machine routing and resource allocation; backup of critical data and network information; resource recovery and reconstruction during virtual machine migration; and restoring the source virtual machine to factory settings to avoid resource conflicts and duplicate runs. This module ensures the rapid and accurate restoration of the virtual machine's operating environment on the target host machine, achieving seamless business migration.

[0065] Data Synchronization Module: This module employs multicast communication to synchronize data between the platform's primary and backup nodes. The main synchronized content includes: task execution records; virtual machine running status and configuration information; and resource usage. This module ensures the consistency of critical data between the primary and backup nodes, providing reliable data support for task takeover after automatic failover.

[0066] Through the coordinated operation of the above modules, this invention realizes a high-availability automatic switching mechanism for the cloud platform management system in the event of a master node failure, ensuring platform-level task continuity and data consistency, and is applicable to critical business scenarios in multi-node cloud management systems.

[0067] like Figure 4 , 5 As shown, the unified control and virtual machine high-availability switching process of the cloud platform includes: 1. Heartbeat monitoring mechanism: Each node periodically executes a heartbeat detection task to continuously monitor the liveness status of the master node within the cluster. Once a master node is detected to have failed to respond multiple times consecutively, the system will automatically determine that it has failed and immediately initiate the master-slave failover process.

[0068] 2. Master Node Election and Virtual IP Switching: The backup node initiates the master node election based on a preemptive election algorithm. After successful election, the winning node will automatically bind to the virtual IP address of the failed master node and notify the network layer via ARP broadcast to achieve fast route redirection and ensure uninterrupted service.

[0069] 3. Activation of main control functions: After taking over, the new master node will immediately activate the unified control module and assume the core business management responsibilities, including: data acquisition module (such as monitoring the running status and resource usage of virtual machines), task scheduling module (such as migration scheduling and status determination), virtual machine migration module (such as smooth switching of critical business), etc.

[0070] 4. Task Recovery Mechanism: The new master node receives and parses the task status information transmitted by the data synchronization module. If any incomplete tasks are found, execution will be automatically resumed according to their progress, ensuring task continuity. If a task fails, the system also supports retrying according to a strategy, improving task stability and robustness.

[0071] 5. High Availability Guarantee for Critical Virtual Machines: When the data acquisition module detects that a critical virtual machine is unavailable, the new master node will immediately initiate the migration process. Critical virtual machines are identified based on preset policy identifiers and business importance configurations, ensuring the stable and continuous operation of core business systems.

[0072] 6. Hot standby node management: Backup nodes that are not selected as the primary node will automatically enter hot standby mode, maintain data synchronization with the primary node, but will not provide services to the outside world. They will be on standby at all times to participate in the next round of primary-standby switchover, thereby improving the overall availability and response speed of the system.

[0073] The embodiments of the present invention address the high-availability automatic failover mechanism for cloud platform management systems, resolving the management complexity and response delays caused by manual switching of primary and backup nodes in traditional systems, thereby enhancing the system's autonomous fault tolerance and continuous operation capabilities. Specifically, it improves system stability and reliability: by constructing an automated primary-backup failover mechanism, it enables rapid and stable switching to the backup node when the primary control node fails, effectively avoiding system unavailability and business interruption; ensures data consistency and task continuity: through an efficient data synchronization mechanism between primary and backup nodes, it ensures that key data such as management status, scheduled tasks, and virtual machine control information remain consistent across nodes, preventing state loss and task duplication; achieves automated and intelligent high-availability control: combining health detection, status awareness, and scheduling logic, it achieves a primary-backup takeover control process without manual intervention, significantly improving the intelligence and response speed of system fault handling; and enhances system self-recovery capabilities and management flexibility: by introducing a unified control module, it can continuously monitor the primary control service, virtual machine status, and host machine resources, automatically scheduling resources and restoring cloud platform management capabilities in case of anomalies, achieving continuous and automated repair of platform services.

[0074] In some embodiments, based on "at least two sets of backup nodes," two independent lease sources (Lease-A / Lease-B) and a monotonically increasing generation number epoch are introduced. Entry is permitted only if the same backup node simultaneously holds valid Lease-A and Lease-B, and successfully generates a new epoch and fencing token. 1. Bind the virtual IP and activate the unified control module; 2. Issue control commands with epoch and fencing_token to subsystems such as storage / task / network; 3. Hardly reject or isolate instructions from lagging epochs or invalid lease sources to prevent split-brain and write isolation after old master node recovery.

[0075] Before starting the primary election, the backup nodes send lease requests to the first lease source and the second lease source respectively, and obtain LA and LB; record their respective TTLs and expiration times. The elected node generates a monotonically increasing epoch (64-bit unsigned integer) and generates a one-time fencing_token from the security module. Activation condition: Both LA and LB are valid and the remaining time tr = min(TTL(LA), TTL(LB)) ≥ τ (security threshold). Otherwise, it only enters the shadow state. Unified verification: All critical operations on shared resources (such as task status submission, metadata writing, snapshot marking, routing injection) must carry <epoch, fencing_token>; the subsystem locally saves the recently confirmed epoch*, and if it receives a request with epoch < epoch*, or the fencing_token does not match, it directly rejects. Storage-level isolation: When the new primary is activated, an exclusive reservation / blacklist instruction is sent to the shared resource layer to ensure that the old primary cannot write to the shared volume or the state library even if it "falsely recovers". Clock and validity guarantee: Use a monotonic hardware timer (such as TSC / HPET or a monotonic source calibrated by PTP) to calculate the remaining lease time to avoid misjudgment caused by system clock rollback; when tr ≤ τ, enter the renewal period, and if the renewal fails, it degrades and deactivates and releases the virtual IP.

[0076] Before selecting the new primary node, the cloud platform management backup nodes obtain lease tokens LA and LB from independent first and second lease sources respectively; only when both LA and LB are within the validity period, are they allowed to bind the virtual IP and activate the new primary node. After the election is successful, a monotonically increasing generation number epoch and a one-time fencing token are generated; all critical control instructions for shared resources carry <epoch, fencing_token>, and if the target subsystem detects that the epoch is lower than the most recently confirmed generation it has or the token is invalid, it rejects the execution of the instruction. When the new primary node is activated, an exclusive access control is sent to the shared resource layer to isolate the old primary node from writing, so that the old primary node cannot write to the shared resources after recovery. The lease validity calculates the remaining time based on a monotonic timer, and when the remaining time is less than the threshold τ, a renewal is triggered; if the renewal fails, the virtual IP is automatically released and it enters the inactive state. Highlight the technical effects, prevent brain split: Dual leases + epoch + fencing form a triple constraint, eliminating "dual primary simultaneous writing" after partition recovery. Strong consistent takeover: With epoch as the global order, all backward instructions of the old primary are rigidly intercepted, avoiding state rollback and task confusion. Engineering verifiable: Consistency verification can be performed by injecting faults such as network partitions / clock rollbacks, and the switching accuracy can be quantitatively evaluated.

[0077] In some embodiments, based on existing indicators such as "health B, synchronization delay D, and network stability E", an online prediction model (e.g., exponential weighting + sequential testing, or Kalman filtering for joint state estimation of CPU / IO / latency) is introduced. When the probability of a failure occurring within the next Δt exceeds a threshold θ, a shadow master node is pre-selected and preheated: pre-synchronization: the hot state increments of the task queue, scheduling context, and critical VMs are synchronized to the shadow master; pre-drift: the differential set of the layer 4 connection / session states (conntrack entries) is mirrored; lossless switching: when the switching conditions are met, only VIP fast switching + differential compensation is performed to keep existing long connections open, achieving zero or near-zero packet loss. Prediction triggering: the collected B1 CPU, B2 memory, B3 disk IO, D1 synchronization delay, E1 connectivity, and E2 packet loss rate are used to construct an observation vector to estimate the master node health state ŝ(t) and its drift trend dŝ / dt online; when P(failure|Δt) ≥ θ or early alarms are triggered L times consecutively, the pre-switching phase is entered. Shadow Master Selection and Warm-up: The shadow master with the highest score is selected according to the existing priority scoring formula (it does not provide external services, only "standby"); the shadow master receives the master node's task queue increment, checkpoint metadata of critical virtual machines, and routing / scheduling context. Connection State Mirroring: A flow_id=(5-tuple, epoch) is established for active connections, and differential entries (added / changed / about to time out) are periodically pushed to the shadow master. The shadow master only forwards external connections after it is "activated". Switchover Execution: When the switchover criteria are met (predicted failure to become active or master node lease expires), the old master's external queue is frozen first, an ARP update is broadcast, and the differential connection table is replayed on the shadow master side. After sequence number compensation based on ΔSEQ / ΔACK, forwarding is resumed to ensure that long connections are not interrupted. Rollback Mechanism: If the warning is lifted (P(fault|Δt)<θ') and no switchover is activated during the period, the differential image on the shadow master is discarded and normal operation is restored, only the low-frequency state baseline is retained.

[0078] In some embodiments, the predictive pre-switchover step involves: online estimation of the master node's health status based on time series data of CPU utilization, memory usage, disk I / O load, data synchronization latency, network connectivity, and packet loss rate; when the predicted probability of a failure occurring within a preset time window Δt is greater than a threshold θ, a shadow master node is selected and preheating is performed. The preheating includes: incremental synchronization of the task queue and scheduling context; generating checkpoint metadata for virtual machines marked as critical services and synchronizing it to the shadow master. The lossless traffic drift includes: mirroring the master node's session state to the shadow master node in a differential manner before switching; during switching, replaying the differential on the shadow master node and performing sequence number compensation to maintain existing connections. If the predicted alarm is cleared and no switchover occurs, the differential session mirror of the shadow master node is discarded and the system reverts to the normal synchronization frequency. Highlighting the technical effectiveness, RTO / RPO is moved forward: the recovery point and recovery time are moved forward to before the failure occurs, achieving an engineering path for "second-level or even sub-second-level" master control switching. Lossless experience: Connection-level differential mirroring + sequence number compensation maintains existing TCP / UDP sessions without interruption, and the business end is "unaware" of the handover. Controllable rollback: Automatic rollback in case of false alarms avoids introducing unnecessary handover jitter.

[0079] The above embodiments demonstrate a proactive approach to recovery capabilities. By analyzing metrics such as CPU and memory to predict faults, shadow master nodes are pre-selected and pre-warmed, significantly reducing recovery time (RTO) and recovery point of origin (RPO) to the second or even sub-second level, minimizing business interruptions. Lossless switching is achieved through incremental synchronization of task queues and critical virtual machine checkpoints, differential image session states, and maintaining long-term connections via sequence number compensation during switching, ensuring a seamless experience for the business end. A flexible rollback mechanism is also included, automatically discarding differential session images after warnings are cleared, avoiding system jitter caused by false alarms, balancing switching efficiency and stability, and significantly improving cloud platform reliability and business continuity.

[0080] Example 1 For a cloud platform with 6 management nodes (1 primary and 5 backup), where the primary node is responsible for overall management of 30 virtual machines on 10 host machines, including 2 critical business virtual machines, Example 1 provides a method for switching control of cloud platform management nodes, including: Step 21, Master Node Fault Detection and Judgment: The master node becomes unresponsive due to a sudden disk I / O failure. The five backup nodes send detection signals containing random checksums at a preset period (e.g., once every 50ms). If they do not receive a response from the master node for three consecutive times (exceeding the fixed time limit of 100ms), the system determines that the master node has failed and triggers the failover process. Step 22, New Master Node Election Process: Five backup nodes immediately suspended their external data processing services, retaining only their election communication functions; after qualification verification, one node was eliminated because its data synchronization delay exceeded the threshold (average delay of 1.2s), and the remaining four nodes entered the election. According to priority formula Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E Calculation: Node C has the best overall performance in terms of hardware resource health (CPU utilization 15%, memory usage 20%), historical takeover success rate (all 3 attempts were successful), data synchronization latency (0.08s), and network stability (connectivity 99.9%, packet loss rate 0.1%), and is selected as the new master node with the highest score; Step 23, Virtual IP Switching and Route Redirection: The system automatically unbinds the original master node from the virtual IP (10.0.0.10), binds it to the network interface of node C, and notifies all host machines and network devices to update the address mapping via ARP broadcast. External access requests to the OA system and customer service system are seamlessly routed to node C. Step 24, Task Takeover and Business Recovery: Node C obtains the synchronization data of the original master node through multicast communication, including: 20 normal operation task records, 5 tasks to be executed (such as host machine resource inspection), and 3 interrupted tasks (including 1 unfinished task of migrating the OA virtual machine to the new host machine). For the interrupted OA virtual machine migration task, node C determines that it is in the resource allocation phase and continues to execute: complete the CPU / memory allocation (8 cores 16GB) of the target host machine 4, back up the OA data and network configuration, and trigger the OA virtual machine on the source host machine 2 to restore factory settings to avoid conflicts; A brief pause was detected in the customer service virtual machine due to a failure of the original master node (CPU usage surged to 95%). Node C prioritized task scheduling and triggered migration through the task scheduling module. Within 3 minutes, it was migrated to the host machine 6 with sufficient resources, and the service returned to normal. The five tasks to be executed are sorted by priority (customer service system log backup takes precedence over non-critical virtual machine snapshots) and scheduled for execution in sequence. During the process, resources are monitored through the host machine management module to avoid overload.

[0081] This invention automatically detects the status of the master node and triggers fault switching, which can quickly select a new master node from the backup nodes without manual intervention, greatly shortening the fault recovery time, avoiding system paralysis caused by single point of failure, and ensuring the continuous operation of the core functions of the cloud platform.

[0082] The virtual IP address binding and ARP broadcast route redirection mechanism enables the new master node to seamlessly take over the network identifier of the original master node. External requests can be automatically routed to the new node without modifying the configuration, realizing that business access is unaware of the master node switch and reducing the impact of business interruption.

[0083] The primary and backup nodes synchronize key data such as task records and virtual machine status in real time through multicast communication mechanism. The new primary node can accurately obtain complete task information and verify its integrity to avoid task loss or duplicate execution. Combined with task status judgment and priority scheduling, it can achieve seamless continuation of unfinished tasks and ensure that business processes are not interrupted.

[0084] The new master node monitors host machine resources in real time and allocates them reasonably to avoid conflicts and waste; it prioritizes critical virtual machine tasks and quickly triggers migration in case of anomalies to ensure the continuous operation of core businesses and improve the risk resistance of high-priority businesses.

[0085] By eliminating unqualified nodes through qualification verification and quantitatively evaluating backup nodes using a multi-dimensional priority formula (hardware health, historical performance, data synchronization quality, etc.), the selected new master node is ensured to have comprehensive advantages, reducing system risks after switching and improving the cluster's resilience.

[0086] like Figure 6 As shown, embodiments of the present invention also provide a cloud platform management node switching control device 20, comprising: Module 21 is used to obtain the status data of the cloud platform management master node; The processing module 22 is used to select a new cloud platform management master node from at least two sets of cloud platform management backup nodes when the status data is faulty; bind the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and complete the route redirection; control the task of the original cloud platform management master node to be switched to the new cloud platform management master node for processing; and control the cloud platform management master node to keep the data synchronized with the cloud platform management backup node.

[0087] Optionally, the status data is a response signal from the cloud platform management master node to the detection signals periodically sent by the cloud platform management backup node.

[0088] Optionally, when the status data indicates a fault, a new cloud platform management master node is selected from at least two groups of cloud platform management backup nodes, including: If the status data shows multiple consecutive unresponsive events, the cloud platform management master node is determined to be faulty. Control all cloud platform management backup nodes to enter election status and start the master node election process; Once successfully selected, the winning cloud platform management backup node becomes the new cloud platform management master node.

[0089] Optionally, control all cloud platform management backup nodes to enter election mode and initiate the master node election process, including: Control all cloud platform management backup nodes to suspend providing data processing services to the outside world, and retain only the communication functions related to the election; Perform qualification verification on each cloud platform management backup node; according to Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E Determine the priority score of each cloud platform's management backup node; in, Z Priority scores are assigned to backup nodes managed by the cloud platform. A To preset the basic level, B For the health of hardware resources, C To ensure the success rate of historical takeovers, D Due to data synchronization delay, E For network connection stability, p 1 As the first weight, p 2 As the second weight, p 3 As the third weight, p 4 As the fourth weight, p 5 It is the fifth weight; The cloud platform management backup node with the highest priority score will be designated as the new cloud platform management master node.

[0090] Optionally, the methods for determining the hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability include: according to B=Y- ( p6 × B 1 +p 7 × B 2 +p 8 × B 3 This involves determining the health of hardware resources for each cloud platform's management backup nodes. in, B To manage the hardware resource health of backup nodes for cloud platforms. Y This represents the highest possible value for hardware resource health. B 1 For CPU utilization, B 2 For memory usage, B 3 Disk I / O load rate, p 6 It is the sixth weight. p 7 It is the seventh weight. p 8 It is the eighth weight; according to C=C 1 / C 2 Determine the historical takeover success rate of each cloud platform's management backup nodes; in, C To improve the historical takeover success rate of backup nodes managed by the cloud platform, C 1 For the number of successful takeovers, C 2 Number of takeover attempts; according to D=1÷ ( 1+D 1 ), determine the data synchronization delay of each cloud platform management backup node; in, D To manage data synchronization latency of backup nodes on the cloud platform, D 1 The average delay in seconds; according to E= ( p 9 × E 1 +p 10 × E 2 ), determine the network connection stability of each cloud platform management backup node; in, ETo ensure the stability of network connectivity for backup nodes managed by the cloud platform, E 1 For network connectivity, E 2 For packet loss rate, p 9 It is the ninth weight. p 10 It is the tenth weight.

[0091] Optionally, the virtual IP address of the original cloud platform management master node is bound to the new cloud platform management master node, and route redirection is completed, including: Remove the binding relationship between the original cloud platform management master node and the virtual IP address; Bind the virtual IP address to the network interface of the new cloud platform management master node; The address mapping update notification is sent to all devices in the network via Address Resolution Protocol (ARP) broadcast, thus completing the route redirection.

[0092] Optionally, controlling the task switching from the original cloud platform management master node to the new cloud platform management master node includes: Control the new cloud platform management master node to obtain tasks synchronized from the original cloud platform management master node; Control the new cloud platform management master node to process the tasks of the original cloud platform management master node.

[0093] It should be noted that this device is a device corresponding to the above method. All implementation methods in the above method embodiments are applicable to this embodiment and can achieve the same technical effect.

[0094] Embodiments of the present invention also provide a computing device, comprising: One or more processors; A storage device for storing one or more programs that, when executed by one or more processors, cause the one or more processors to perform the method as described above.

[0095] Embodiments of the present invention also provide a computing device readable storage medium storing instructions that, when executed on a computing device, cause the computing device to perform the method described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effect.

[0096] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computing device software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0097] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0098] In the embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0099] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0100] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0101] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computing device-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computing device software product is stored in a storage medium and includes several instructions to cause a computing device (which may be a personal computing device, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0102] Furthermore, it should be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of the present invention. Moreover, the steps performing the above-described series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof. This is something that those skilled in the art can achieve using basic programming skills after reading the description of the present invention.

[0103] Therefore, the object of the present invention can also be achieved by running a program or a set of programs on any computing device. The computing device can be a known general-purpose device. Therefore, the object of the present invention can also be achieved simply by providing a program product containing program code implementing the method or apparatus. That is, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent to the present invention. Furthermore, the steps performing the above series of processes can naturally be performed in the order described, but are not necessarily required to be performed in chronological order. Some steps can be performed in parallel or independently of each other.

[0104] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method for switching control of cloud platform management nodes, characterized in that, include: Obtain the status data of the cloud platform management master node; The status data is a response signal from the cloud platform management master node to the detection signals periodically sent by the cloud platform management backup node; The detection signal includes a timestamp, a backup node identifier, a random checksum, and the sequence number of this detection. After receiving the detection signal, the cloud platform management master node immediately verifies the validity of the random checksum and generates a response signal within a fixed time limit. The response signal includes the master node identifier, confirmation information corresponding to the current detection sequence number, the running status of the master node's current core processes, and a snapshot of the critical resource utilization rate. When the status data indicates a fault, a new cloud platform management master node is elected from at least two sets of cloud platform management backup nodes; Bind the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and complete the route redirection; The task of the original cloud platform management master node is switched to the new cloud platform management master node for processing; and the cloud platform management master node and the cloud platform management backup node are kept in data synchronization. When the status data indicates a fault, a new cloud platform management master node is elected from at least two groups of cloud platform management backup nodes, including: If the status data shows multiple consecutive unresponsive events or multiple consecutive critical resource utilization rates exceeding a preset threshold, the cloud platform management master node is determined to be faulty. Control all cloud platform management backup nodes to enter election status and start the master node election process; After the election is successful, the winning cloud platform management backup node becomes the new cloud platform management master node; This includes controlling all cloud platform management backup nodes to enter election mode and initiating the master node election process, including: Control all cloud platform management backup nodes to suspend providing data processing services to the outside world, and retain only the communication functions related to the election; Perform qualification verification on each cloud platform management backup node; according to Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E Determine the priority score of each cloud platform's management backup node; in, Z Priority scores are assigned to backup nodes managed by the cloud platform. A To preset the basic level, B For the health of hardware resources, C To ensure the success rate of historical takeovers, D Due to data synchronization delay, E For network connection stability, p 1 As the first weight, p 2 As the second weight, p 3 As the third weight, p 4 As the fourth weight, p 5 It is the fifth weight; The cloud platform management backup node with the highest priority score will be designated as the new cloud platform management master node. The methods for determining the hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability include: according to B=Y- ( p 6 × B 1 +p 7 × B 2 +p 8 × B 3 This involves determining the health of hardware resources for each cloud platform's management backup nodes. in, B To manage the hardware resource health of backup nodes for the cloud platform. Y This represents the highest possible value for hardware resource health. B 1 For CPU utilization, B 2 For memory usage, B 3 Disk I / O load rate, p 6 It is the sixth weight. p 7 It is the seventh weight. p 8 It is the eighth weight; according to C=C 1 / C 2 Determine the historical takeover success rate of each cloud platform's management backup nodes; in, C To improve the historical takeover success rate of backup nodes managed by the cloud platform, C 1 For the number of successful takeovers, C 2 Number of takeover attempts; according to D=1÷ ( 1+D 1 ), determine the data synchronization delay of each cloud platform management backup node; in, D To manage data synchronization latency of backup nodes on the cloud platform, D 1 The average delay in seconds; according to E= ( p 9 × E 1 +p 10 × E 2 ), determine the network connection stability of each cloud platform management backup node; in, E To ensure the stability of network connectivity for backup nodes managed by the cloud platform, E 1 For network connectivity, E 2 For packet loss rate, p 9 It is the ninth weight. p 10 It is the tenth weight; This involves binding the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and completing route redirection, including: Remove the binding relationship between the original cloud platform management master node and the virtual IP address; Bind the virtual IP address to the network interface of the new cloud platform management master node; The address mapping update notification is sent to all devices in the network via ARP broadcast to complete the route redirection. The process of switching the task of controlling the original cloud platform management master node to the new cloud platform management master node includes: Control the new cloud platform management master node to obtain tasks synchronized from the original cloud platform management master node; Control the new cloud platform management master node to process the tasks of the original cloud platform management master node.

2. A switching control device for a cloud platform management node, characterized in that, include: The acquisition module is used to acquire status data of the cloud platform management master node; The status data is a response signal from the cloud platform management master node to the detection signals periodically sent by the cloud platform management backup node; the detection signal includes a timestamp, backup node identifier, random checksum, and the sequence number of this detection; after receiving the detection signal, the cloud platform management master node immediately verifies the validity of the random checksum and generates a response signal within a fixed time limit; the response signal includes the master node identifier, confirmation information corresponding to the current detection sequence number, the running status of the master node's current core processes, and a snapshot of the critical resource utilization rate; The processing module is used to elect a new cloud platform management master node from at least two groups of cloud platform management backup nodes when the status data indicates a fault. Bind the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and complete the route redirection; control the task switching of the original cloud platform management master node to the new cloud platform management master node for processing; and control the cloud platform management master node to keep data synchronized with the cloud platform management backup node; When the status data indicates a fault, a new cloud platform management master node is elected from at least two groups of cloud platform management backup nodes, including: If the status data shows multiple consecutive unresponsive events or multiple consecutive critical resource utilization rates exceeding a preset threshold, the cloud platform management master node is determined to be faulty. Control all cloud platform management backup nodes to enter election status and start the master node election process; After the election is successful, the winning cloud platform management backup node becomes the new cloud platform management master node; This includes controlling all cloud platform management and backup nodes to enter election mode and initiating the master node election process, including: Control all cloud platform management backup nodes to suspend providing data processing services to the outside world, and retain only the communication functions related to the election; Perform qualification verification on each cloud platform management backup node; according to Z = p 1 × A + p 2 × B + p 3 × C + p 4 × D + p 5 × E Determine the priority score of each cloud platform's management backup node; in, Z Priority scores are assigned to backup nodes managed by the cloud platform. A To preset the basic level, B For the health of hardware resources, C To ensure the success rate of historical takeovers, D Due to data synchronization delay, E For network connection stability, p 1 As the first weight, p 2 As the second weight, p 3 As the third weight, p 4 As the fourth weight, p 5 It is the fifth weight; The cloud platform management backup node with the highest priority score will be designated as the new cloud platform management master node. The methods for determining the hardware resource health, historical takeover success rate, data synchronization latency, and network connection stability include: according to B=Y- ( p 6 × B 1 +p 7 × B 2 +p 8 × B 3 This involves determining the health of hardware resources for each cloud platform's management backup nodes. in, B To manage the hardware resource health of backup nodes for the cloud platform. Y This represents the highest possible value for hardware resource health. B 1 For CPU utilization, B 2 For memory usage, B 3 Disk I / O load rate, p 6 It is the sixth weight. p 7 It is the seventh weight. p 8 It is the eighth weight; according to C=C 1 / C 2 Determine the historical takeover success rate of each cloud platform's management backup nodes; in, C To improve the historical takeover success rate of backup nodes managed by the cloud platform, C 1 For the number of successful takeovers, C 2 Number of takeover attempts; according to D=1÷ ( 1+D 1 ), determine the data synchronization delay of each cloud platform management backup node; in, D To manage data synchronization latency of backup nodes on the cloud platform, D 1 The average delay in seconds; according to E= ( p 9 × E 1 +p 10 × E 2 ), determine the network connection stability of each cloud platform management backup node; in, E To ensure the stability of network connectivity for backup nodes managed by the cloud platform, E 1 For network connectivity, E 2 For packet loss rate, p 9 It is the ninth weight. p 10 It is the tenth weight; This involves binding the virtual IP address of the original cloud platform management master node to the new cloud platform management master node and completing route redirection, including: Remove the binding relationship between the original cloud platform management master node and the virtual IP address; Bind the virtual IP address to the network interface of the new cloud platform management master node; The address mapping update notification is sent to all devices in the network via Address Resolution Protocol (ARP) broadcast to complete the route redirection. The process of switching the task of controlling the original cloud platform management master node to the new cloud platform management master node includes: Control the new cloud platform management master node to obtain tasks synchronized from the original cloud platform management master node; Control the new cloud platform management master node to process the tasks of the original cloud platform management master node.

3. A computing device, characterized in that, include: One or more processors; A storage device for storing one or more programs that, when executed by one or more processors, cause the one or more processors to perform the method as described in claim 1.

4. A computing device readable storage medium, characterized in that, The computing device readable storage medium stores a program that, when executed by a processor, implements the method as described in claim 1.

Images