A distributed system software upgrade method

Abstract

The present application discloses a distributed system software upgrade method. Compared with the traditional server-side synchronous upgrade method, the method places high demands on the concurrency and bandwidth of the server side. Once a failure or abnormality occurs on the server side, the upgrade work of the entire system may not proceed smoothly. The multiple client nodes are respectively assigned to different areas, and the operation and maintenance server allocates a corresponding regional multicast address to each area in the address pool; each area selects one of the client nodes as the regional virtual server within the current cycle; the regional virtual server receives the upgrade request from the central upgrade module of the operation and maintenance server, and after successfully downloading the upgrade package, it verifies the integrity of the current upgrade package; and continuously sends the latest software version information according to the established period through the regional multicast address. The present application significantly improves the upgrade efficiency and enhances the fault tolerance of the system, thereby efficiently, stably and reliably performing distributed system software upgrades.

Description

Technical Field

[0001] The present application relates to the technical field of software upgrade, and in particular to a software upgrade method for a distributed system. Background Art

[0002] Software upgrades are crucial for ensuring continued effective operation, meeting diverse user needs, and enhancing security and performance. They play an essential role in improving system robustness. In large-scale systems, tens of thousands of devices operate collaboratively. To ensure the consistency and stability of overall system functionality, these devices often require software with unified functional versions. Consequently, simultaneous upgrades of multiple devices have become an unavoidable and crucial requirement during large-scale system maintenance and updates.

[0003] In the traditional server-side synchronous upgrade model, the software upgrade process follows specific steps. First, the client actively requests the operating environment parameters required for the software to be upgraded from the server. The client then embeds these parameters in an upgrade request and sends it to the server. Upon receiving the upgrade request, the server matches and sends the corresponding client software upgrade package based on the operating environment parameters included in the request. Finally, the client uses the received upgrade package to complete the software upgrade.

[0004] However, in scenarios like computer rooms where a large number of devices require simultaneous upgrades, traditional server-side synchronous upgrade methods present significant challenges. For one thing, this approach places high demands on server concurrency and bandwidth. Because numerous clients simultaneously initiate upgrade requests, the server must possess robust concurrent processing capabilities to ensure timely response to each request. Furthermore, the transmission of large numbers of upgrade packages requires ample bandwidth. Furthermore, any server-side failure or anomaly is highly likely to negatively impact the client upgrade process, potentially even preventing the entire system upgrade from proceeding smoothly. This heavy reliance on the server undoubtedly increases the risk and instability of the system upgrade process. Summary of the Invention

[0005] The present application provides a distributed system software upgrade method, which aims to solve the problem that traditional server-side synchronous upgrade methods have high requirements on concurrency and bandwidth on the server side; and once a failure or abnormality occurs on the server side, it is very likely to have a negative impact on the client's upgrade process, and may even cause the upgrade work of the entire system to be unable to proceed smoothly.

[0006] In a first aspect, a distributed system software upgrade method is provided, wherein the distributed system includes an operation and maintenance server and multiple client nodes; the multiple client nodes are respectively assigned to different areas, and the operation and maintenance server allocates a corresponding regional multicast address to each area in the address pool; the client nodes in each area jointly elect one of the client nodes as the regional virtual server through internal request interaction according to device resources and network status within the current cycle, and monitor the operating status of the regional virtual server in real time within a cycle. When the regional virtual server is abnormal, a new regional virtual server node is re-elected in the current area.

[0007] The distributed system software upgrade method is applied to a regional virtual server and includes the following steps A1 to A3.

[0008] Step A1: Receive an upgrade request from the operation and maintenance server, parse the request content, and obtain the upgrade package information therefrom; at the same time, based on the software version information of all other client nodes stored in itself, determine whether all other client nodes in the current area need to upgrade their software; if no upgrade is required, feedback is sent to the operation and maintenance server to inform it that the local area has the latest version and no upgrade operation is required; if an upgrade is required, a download request is initiated to the server according to the server address specified in the upgrade package information to obtain the corresponding upgrade package; wherein, the upgrade package information includes the version number of the upgrade package, the applicable software version range, the upgrade content summary, and the download path.

[0009] Step A2: After successfully downloading the upgrade package, verify the integrity of the current upgrade package. If there is an abnormality in the upgrade package, notify the operation and maintenance server of the abnormality. If the upgrade package is complete and correct, store the upgrade package in the designated local storage location and update the software version information carried in its own periodic broadcast message to ensure that the software version information transmitted to other client nodes in the area is the latest.

[0010] Step A3: After completing the storage of the upgrade package and the updating of the software version information, the latest software version information is continuously sent through the regional multicast address according to a predetermined period.

[0011] In the above solution, optionally, the multiple client nodes are respectively assigned to different areas, which specifically include the following contents.

[0012] Preset the number of nodes T in the current distributed system and the maximum number of nodes M in each region; based on the number of nodes T and the maximum number of nodes M, the operation and maintenance server calculates the total number of regions At the same time, the operation and maintenance server allocates a unique multicast address to each area in the address pool.

[0013] When the operation and maintenance server receives an online request from any client node, the number of online nodes S will automatically increase, which will be used to calculate the partition index value of the client node in the future. When S is less than N, the operation and maintenance server will partition the client nodes in the order in which they come online and notify the current node of the multicast address to generate the optimal node array in the region. , this array is used to store the comprehensive score of each node and the corresponding multicast address.

[0014] When S is greater than or equal to N, the operation and maintenance server uses the formula Calculate the index value a of the initial assigned area corresponding to the current client node; then, for the newly online client node, compare its comprehensive score with the existing nodes in the array R; if the new node If the comprehensive score of is lower than all nodes in R, the new node is notified to use the multicast address of area a; The comprehensive score of is higher than some nodes in array R, then select the node with the lowest score from these nodes. , and notify the new node to use The multicast address of array R is replaced The comprehensive score of the node is , and swap the elements in the array and , to ensure that the array R can always reflect the optimal node situation in the current area, thereby effectively avoiding the problem of large performance gaps between regions.

[0015] In the above scheme, optionally, the comprehensive scoring rule is to perform a comprehensive scoring based on the current device load, remaining network bandwidth, packet loss rate, remaining disk capacity, and number of past selections, calculate a corresponding score for each node device, and select the node with the highest score as the regional virtual server node; specifically including the following contents.

[0016] The evaluation factor set is: .

[0017] Factor weight sets: ,in, Representation factors The weight of .

[0018] Using operators: ,calculate Average value within a period, where k is a constant and represents the number of statistics within a statistical period.

[0019] Using operators: , calculate the result value of the number of times selected in the past statistical period.

[0020] Calculate the comprehensive score: Here, m represents the critical value of the remaining disk capacity.

[0021] In the above solution, optionally, each region selects one of the client nodes as a regional virtual server in the current cycle, which specifically includes the following steps S1 to S6.

[0022] In step S1, any two client nodes in the region are recorded as the first client node and the second client node. After the first client node and the second client node complete the regional allocation, they each obtain the operating system version and software version of the client node, calculate the comprehensive score of the client node, and broadcast it within the regional multicast address according to the established period.

[0023] In step S2, after receiving the node information of the first client node, the second client node stores the operating system version and software version number of the first client node, and compares the comprehensive scores of the first client node and the current client node; the second client node determines whether the current client node is qualified to serve as a regional server for the current region based on the comprehensive scores; if qualified, the current client node proceeds to the next step as a regional server; otherwise, no other operations are performed and the client node continues to monitor the broadcast data of other client nodes.

[0024] Step S3: When the second client serves as the regional server, the synchronization message of the regional multicast address is reassembled and the regional server identifier is added.

[0025] In step S4, after the first client node receives the multicast message from the second client node carrying the regional virtual server identifier, it compares the current client node with the second client node to determine whether the current client node is more suitable to serve as the regional virtual server than the second client node; if the current client node is more suitable, that is, it disagrees with the identity of the second client node, it sends a notification of failure of the regional virtual server application to the second client; at the same time, it updates the regional multicast message and designates the regional virtual server as the current client node; if the second client node is suitable to serve as the regional virtual server, no operation is performed.

[0026] Step S5: When the second client node receives the regional virtual server application failure message sent by the first client node, the second client node immediately stops sending the regional server identifier on the regional multicast address and enters the receiving state to wait for subsequent related information.

[0027] In step S6, the second client node is in a receiving state and, upon receiving a broadcast request from the regional server of the first client node, initiates a timed link detection function. During the detection process, if the first client node is detected to be offline, the process of steps S2 to S5 is repeated and the regional server is re-determined. If the second client node is not detected to be offline, the second client node continues to monitor the broadcast information of the regional multicast address.

[0028] In the above solution, optionally, during an election cycle, unless the node serving as the regional server changes, the node will not be re-elected as the regional server.

[0029] In the above solution, optionally, the regional virtual server further comprises: receiving the upgrade results reported by each client node in real time, summarizing and collating them regularly, and reporting to the operation and maintenance server at predetermined time intervals.

[0030] In the above solution, optionally, the operation and maintenance server monitors and summarizes the upgrade results of each node reported by the regional server in real time, and notifies the operation and maintenance personnel to perform manual intervention when an abnormality occurs.

[0031] In the above scheme, optionally, the integrity verification of the current upgrade package includes: using a CRC verification method to verify the integrity of the current upgrade package: by calculating the cyclic redundancy check code of the upgrade package data and comparing it with a preset check value, so as to determine whether there is any abnormal situation of data loss or damage in the transmission process of the upgrade package.

[0032] On the second aspect, a distributed system software upgrade method is provided, wherein the distributed system includes an operation and maintenance server and multiple client nodes; the multiple client nodes are respectively assigned to different areas, and the operation and maintenance server will allocate a corresponding regional multicast address for each area in the address pool; the client nodes in each area jointly elect one of the client nodes as the regional virtual server through internal request interaction based on device resources and network status within the current cycle, and monitor the operating status of the regional virtual server in real time within a cycle. When the regional virtual server is abnormal, a new regional virtual server node is re-elected in the current area.

[0033] The distributed system software upgrade method is applied to any other client node except the one used as a regional virtual server, and includes the following steps B1 to B3.

[0034] Step B1: The regional virtual server continuously broadcasts the upgrade package information on the regional broadcast address according to a preset period.

[0035] In step B2, the client node receives an upgrade request from the regional virtual server, compares its current software version with the version requirement specified in the upgrade package information, and determines whether it needs to be upgraded. If no upgrade is required, a feedback message is sent to the regional virtual server to inform it that no upgrade is required. If an update is required, a download request is initiated to the server based on the specified server address provided in the upgrade package information to obtain the corresponding upgrade package.

[0036] Step B3: After successfully downloading the upgrade package, verify the integrity of the upgrade package. If there is an abnormality in the upgrade package, send a notification to the regional virtual server to inform it that the upgrade package has an abnormality. If the upgrade package is complete and correct, start the software upgrade operation according to the established upgrade process. After the software upgrade is completed, report the upgrade results to the regional virtual server.

[0037] In the above scheme, further optionally, the regional virtual server continuously broadcasts the upgrade package information on the regional broadcast address according to a preset period, and the broadcast information includes detailed information of the upgrade package, status information of the regional virtual server and the upgrade request; the client node receives the broadcast information from the regional virtual server, parses the broadcast information, and extracts detailed information of the upgrade package and the upgrade request; the client node determines whether it needs to perform an upgrade operation based on the upgrade request.

[0038] Compared with the prior art, this application has at least the following beneficial effects.

[0039] Based on further analysis and research on existing technical problems, this application recognizes that the traditional server-side synchronous upgrade method places high demands on the concurrency and bandwidth of the server; and once a failure or abnormality occurs on the server, it is very likely to have a negative impact on the upgrade process of the client, and may even cause the upgrade of the entire system to be unable to proceed smoothly. By dividing the regions and allocating multicast addresses through the operation and maintenance server, the client recommends the regional server according to the comprehensive scoring rules. The regional server receives the upgrade request and manages the upgrade package, and monitors the upgrade process through a real-time feedback mechanism. This application significantly improves the upgrade efficiency, enhances the system's fault tolerance, and optimizes resource utilization, thereby achieving an efficient, stable and reliable distributed system software upgrade effect.

[0040] The present application also provides a method for electing regional servers in a distributed system. By means of technical means such as the client joining the region and broadcasting its own information, receiving and comparing node information, dynamically electing regional servers, and performing periodic link detection and re-election, the method achieves technical effects such as efficient regional server election, dynamic adjustment and fault tolerance, real-time monitoring and feedback, and optimized resource utilization, thereby ensuring that the distributed system can operate stably and efficiently when nodes change dynamically.

[0041] In the election decision-making dimension, this solution breaks through the limitations of traditional single indicators or weighted averages and innovatively constructs a four-dimensional evaluation model. This model incorporates real-time performance parameters such as device idle rate, remaining bandwidth, and transmission success rate, and introduces the number of elections within a statistical period as a historical stability indicator. Using a time-series data smoothing algorithm, this model weights instantaneous resource fluctuations, effectively mitigating election bias caused by sudden network traffic bursts and temporary equipment failures, significantly improving the scientific nature and sustainability of election results.

[0042] This application also has the following advantages.

[0043] 1. Use the regional division mechanism to achieve reasonable division based on multiple factors.

[0044] 2. A cluster head selection algorithm that comprehensively considers multiple factors ensures the selection of a suitable cluster head, and the upgrade pressure is distributed from the traditional central server to the regional servers.

[0045] 3. Regional servers can be recommended in real time. When the original server fails, a new server can be quickly recommended to avoid the inability to upgrade other devices in the system due to server failure.

[0046] 4. Each upgrade client reports the upgrade results in real time. Compared with traditional upgrade methods, it can accurately locate abnormal devices and reduce labor and time costs.

[0047] 5. A dynamic, adaptive election strategy is employed to periodically monitor cluster head node activity and stress parameters, enabling real-time health assessment of cluster head nodes. When node performance degradation or overload is detected, the system automatically triggers a re-election process, ensuring that the cluster head role remains with the optimal node. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 A flowchart of a distributed system software upgrade method provided in one embodiment of the present application.

[0049] Figure 2 A software upgrade deployment diagram provided for one embodiment of the present application.

[0050] Figure 3 A flowchart of the election area server provided in one embodiment of the present application.

[0051] Figure 4 A flowchart of a regional server upgrade provided in one embodiment of the present application.

[0052] Figure 5 This is a regional client upgrade process provided by one embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0054] In the description of this application: unless otherwise specified, "plurality" means two or more. The terms "first," "second," "third," etc. in this application are intended to distinguish the objects referred to and do not have any special technical connotations (for example, they should not be understood as emphasizing importance or order). Expressions such as "including," "comprising," and "having" also mean "not limited to" (certain units, components, materials, steps, etc.).

[0055] Given the problems with traditional server-side synchronous upgrade methods, as described in the background, this application proposes a highly efficient software upgrade method suitable for distributed systems. This method aims to address the server's reliance on high concurrency and high bandwidth. Through an innovative upgrade architecture, it reduces the pressure on the server when simultaneously upgrading a large number of devices. Furthermore, this application aims to prevent client upgrade failures due to server-side anomalies, enhance the stability and reliability of system upgrades, and ensure that clients can successfully complete software upgrades in all situations.

[0056] In one embodiment, a distributed system software upgrade method is provided, wherein the distributed system includes an operation and maintenance server and multiple client nodes; the multiple client nodes are respectively assigned to different areas, and the operation and maintenance server allocates a corresponding regional multicast address to each area in an address pool; the client nodes in each area jointly elect one of the client nodes as a regional virtual server through internal request interaction based on device resources and network status within the current cycle, and monitor the operating status of the regional virtual server in real time within a cycle. When the regional virtual server is abnormal, a new regional virtual server node is re-elected in the current area.

[0057] The distributed system software upgrade method is applied to a regional virtual server and includes the following steps A1 to A3.

[0058] Step A1: Receive an upgrade request from the operation and maintenance server, parse the request content, and obtain the upgrade package information from it; at the same time, based on the software version information of all other client nodes stored in itself, determine whether all other client nodes in the current area need to upgrade their software; if no upgrade is required, feedback is sent to the operation and maintenance server to inform it that the local area has the latest version and no upgrade operation is required; if an upgrade is required, a download request is initiated to the server according to the server address specified in the upgrade package information to obtain the corresponding upgrade package; the upgrade package information includes the version number of the upgrade package, the applicable software version range, the upgrade content summary, and the download path.

[0059] Step A2: After successfully downloading the upgrade package, verify the integrity of the current upgrade package. If there is an abnormality in the upgrade package, notify the operation and maintenance server of the abnormality. If the upgrade package is complete and correct, store the upgrade package in the designated local storage location and update the software version information carried in its own periodic broadcast message to ensure that the software version information transmitted to other client nodes in the area is the latest.

[0060] Step A3: After completing the storage of the upgrade package and the updating of the software version information, the latest software version information is continuously sent through the regional multicast address according to a predetermined period.

[0061] In this embodiment, this application proposes a new distributed system software upgrade method. By introducing the concept of "regional virtual servers," this method distributes upgrade tasks to various regions, reducing the pressure on operation and maintenance servers. Using regional multicast addresses to disseminate upgrade information improves information transmission efficiency and reduces network bandwidth usage. Local storage and verification mechanisms ensure the integrity and reliability of upgrade packages, preventing upgrade failures due to server-side anomalies.

[0062] This application proposes a distributed system software upgrade method, which solves the problems existing in traditional upgrade methods by introducing regional virtual servers and multicast technology, improves upgrade efficiency and stability, and is suitable for software upgrade scenarios of large-scale distributed systems.

[0063] In one embodiment, multiple client nodes are respectively assigned to different areas, specifically including the following.

[0064] Preset the number of nodes T in the current distributed system and the maximum number of nodes M in each region; based on the number of nodes T and the maximum number of nodes M, the operation and maintenance server calculates the total number of regions At the same time, the operation and maintenance server allocates a unique multicast address to each area in the address pool.

[0065] When the operation and maintenance server receives an online request from any client node, the number of online nodes S will automatically increase, which will be used to calculate the partition index value of the client node in the future. When S is less than N, the operation and maintenance server will partition the client nodes in the order in which they come online and notify the current node of the multicast address to generate the optimal node array in the region. ,This array is used to store the comprehensive score of each node and the corresponding multicast address.

[0066] When S is greater than or equal to N, the operation and maintenance server uses the formula Calculate the index value a of the initial assigned area corresponding to the current client node; then, for the newly online client node, compare its comprehensive score with the existing nodes in the array R; if the new node If the comprehensive score of is lower than all nodes in R, the new node is notified to use the multicast address of area a; The comprehensive score of is higher than some nodes in array R, then select the node with the lowest score from these nodes. , and notify the new node to use The multicast address of array R is replaced The comprehensive score of the node is , and swap the elements in the array and , to ensure that the array R can always reflect the optimal node situation in the current area, thereby effectively avoiding the problem of large performance gaps between regions.

[0067] In this embodiment, it is assumed that the system has the following parameters: the total number of nodes T = 10, the maximum number of nodes in each area M = 3; the total number of areas The operation and maintenance server will divide the area according to the following steps.

[0068] Client 1 comes online: S = 1. Because S < N (1 < 4), the operation and maintenance server assigns client 1 to area 1 and tells client 1 to use area 1's multicast address.

[0069] Client 4 comes online: S = 4. Because S = N (4 = 4), the operation and maintenance server calculates the partition index value a = 4%4 = 4÷4 = 1 with a remainder of 0, assigns client 4 to area 4, and notifies client 4 to use area 4's multicast address.

[0070] When the fifth client comes online: the number of online nodes S=5.

[0071] Calculate the index value a of the current range: a = 5 % 4 = 5 ÷ 4 = 1 with a remainder of 1. % is an operator, usually representing a "modulo" operation. The result of a modulo operation is the remainder after dividing two numbers.

[0072] Therefore, the index value of the current area a=1, that is, the fifth client is initially assigned to area 1.

[0073] If the 6th client comes online: the number of online nodes S=6.

[0074] Calculate the index value a of the current area: a=6%4=6÷4=1 remainder 2.

[0075] Therefore, the index value of the current area a=2, that is, the sixth client is initially assigned to area 2.

[0076] Assume that the comprehensive scores of the nodes in array R are as follows: node 1: 80; node 2: 75; node 3: 90; node 4: 85.

[0077] New node 5 comes online with an overall score of 95. The system performs the following operations.

[0078] Comparing the comprehensive scores: The comprehensive score of node 5 (95) is higher than the comprehensive scores of some nodes in array R (80, 75, 85).

[0079] Select the node with the lowest score: Select the node with the lowest comprehensive score from these nodes (node ​​2, comprehensive score 75).

[0080] Notify new nodes: Notify node 5 to use the multicast address of the current area.

[0081] Update array R: Replace the comprehensive score of node 2 in array R with the comprehensive score of node 5 (95), and update the elements in array R.

[0082] Updated array R: Node 1: 80; Node 5: 95; Node 3: 90; Node 4: 85.

[0083] In this embodiment, regional division not only considers the order in which devices come online, but also incorporates a comprehensive score based on multiple factors, including current device load, network bandwidth, packet loss rate, and disk capacity, to ensure relatively balanced node performance within each region. Regional division is dynamic; as new devices come online or existing devices go offline, the system recalculates and adjusts the regional divisions to ensure system stability and efficiency. By rationally allocating nodes to different regions, we avoid overloading some areas while underloading others, optimizing resource utilization across the entire system.

[0084] The regional division method in this application achieves load balancing and performance optimization by combining a multi-factor comprehensive scoring and dynamic adjustment mechanism. This division method not only considers the order in which devices are online, but also takes into account the current performance status of the devices, ensuring relatively balanced performance of nodes within each region, thereby improving the efficiency and stability of the entire distributed software upgrade system.

[0085] In one embodiment, a comprehensive score is performed based on the current device load, remaining network bandwidth, packet loss rate, remaining disk capacity, and the number of past selections, and a corresponding score is calculated for each node device, and the node with the highest score is selected as the regional virtual server node; specifically, the following contents are included.

[0086] The evaluation factor set is: .

[0087] Factor weight sets: in, Representation factors The weight of .

[0088] Using operators: ,calculate Average value within a period, where k is a constant and represents the number of statistics within a statistical period.

[0089] Using operators: , calculate the result value of the number of times selected in the past statistical period.

[0090] Calculate the comprehensive score: Here, m represents the critical value of the remaining disk capacity.

[0091] In one embodiment, each region elects one of its client nodes as a regional virtual server in the current cycle, which specifically includes the following steps S1 to S6.

[0092] In step S1, any two client nodes in the region are recorded as the first client node and the second client node. After the first client node and the second client node complete the regional allocation, they each obtain the operating system version and software version of the client node, calculate the comprehensive score of the client node, and broadcast it within the regional multicast address according to the established period.

[0093] In step S2, after receiving the node information of the first client node, the second client node stores the operating system version and software version number of the first client node, and compares the comprehensive scores of the first client node and the current client node; the second client node determines whether the current client node is qualified to serve as a regional server for the current region based on the comprehensive scores; if qualified, the current client node proceeds to the next step as a regional server; otherwise, no other operations are performed and the client node continues to monitor the broadcast data of other client nodes.

[0094] Step S3: When the second client serves as the regional server, the synchronization message of the regional multicast address is reassembled and the regional server identifier is added.

[0095] In step S4, after the first client node receives the multicast message from the second client node carrying the regional virtual server identifier, it compares the current client node with the second client node to determine whether the current client node is more suitable to serve as the regional virtual server than the second client node; if the current client node is more suitable, that is, it disagrees with the identity of the second client node, it sends a notification of failure of the regional virtual server application to the second client; at the same time, it updates the regional multicast message and designates the regional virtual server as the current client node; if the second client node is suitable to serve as the regional virtual server, no operation is performed.

[0096] Step S5: When the second client node receives the regional virtual server application failure message sent by the first client node, the second client node immediately stops sending the regional server identifier on the regional multicast address and enters the receiving state to wait for subsequent related information.

[0097] In step S6, the second client node is in a receiving state and, upon receiving a broadcast request from the regional server of the first client node, initiates a timed link detection function. During the detection process, if the first client node is detected to be offline, the process of steps S2 to S5 is repeated and the regional server is re-determined. If the second client node is not detected to be offline, the second client node continues to monitor the broadcast information of the regional multicast address.

[0098] In this embodiment, the upgrade and election are controlled separately. If the upgrade process happens to cross the time node of the regional server re-election, the original regional server can be used without affecting the election. After the upgrade is completed, the newly elected regional server will be used.

[0099] Version information is distributed via multicast. After the election, non-regional servers stop listening on the operations server's listening address and instead listen on the elected multicast address. Regional servers receive multicast messages from the operations server, and regional clients receive multicast messages from the regional server. Upgrade packages are distributed via multicast and are downloaded via FTP.

[0100] The regional server verifies and stores the upgrade package before performing the upgrade. The upgrade software is independent of the system software, so the upgrade of the system software will not affect the information synchronization of this software.

[0101] In this embodiment, the terms "first client node" and "second client node" are merely illustrative terms used to describe the functions and tasks of different client nodes during the selection of a regional virtual server. They do not limit the number of client nodes, nor do they imply a fixed identity or role for client nodes. In practice, any client node can assume the functions of "first client node" or "second client node," and these functions can be dynamically switched between different client nodes.

[0102] In one embodiment, during an election cycle, unless the node serving as the regional server changes, the node will not be re-elected as the regional server.

[0103] In one embodiment, the regional virtual server further includes: receiving the upgrade results reported by each client node in real time, summarizing and collating them regularly, and reporting them to the operation and maintenance server at predetermined time intervals.

[0104] In one embodiment, the operation and maintenance server monitors and summarizes the upgrade results of each node reported by the regional server in real time. If an abnormality occurs, the operation and maintenance server notifies the operation and maintenance personnel to perform manual intervention.

[0105] In one embodiment, verifying the integrity of the current upgrade package includes: verifying the integrity of the current upgrade package using a CRC check method: by calculating a cyclic redundancy check code of the upgrade package data and comparing it with a preset check value, thereby determining whether the upgrade package has any abnormal conditions such as data loss or damage during transmission.

[0106] In this embodiment, the CRC check method is described only as an example and is not a specific limitation on the verification scheme. The user can select any appropriate verification method according to actual needs, such as MD5, SHA-1, SHA-256, SHA-512, HMAC, or any other verification algorithm that can ensure data integrity. This application does not limit the specific verification method, and all methods that can achieve data integrity verification are within the scope of protection of this application.

[0107] In one embodiment, a distributed system includes an operation and maintenance server and multiple client nodes; the characteristic is that the multiple client nodes are respectively assigned to different areas, and the operation and maintenance server will allocate a corresponding regional multicast address for each area in the address pool; the client nodes in each area jointly elect one of the client nodes as the regional virtual server through internal request interaction based on device resources and network status within the current cycle, and monitor the operating status of the regional virtual server in real time within a cycle. When the regional virtual server is abnormal, a new regional virtual server node is re-elected in the current area.

[0108] The distributed system software upgrade method is applied to any other client node except the one used as a regional virtual server, and includes the following steps B1 to B3.

[0109] Step B1: The regional virtual server continuously broadcasts the upgrade package information on the regional broadcast address according to a preset period.

[0110] In step B2, the client node receives an upgrade request from the regional virtual server, compares its current software version with the version requirement specified in the upgrade package information, and determines whether it needs to be upgraded. If no upgrade is required, a feedback message is sent to the regional virtual server to inform it that no upgrade is required. If an update is required, a download request is initiated to the server based on the specified server address provided in the upgrade package information to obtain the corresponding upgrade package.

[0111] Step B3: After successfully downloading the upgrade package, verify the integrity of the upgrade package. If there is an abnormality in the upgrade package, send a notification to the regional virtual server to inform it that the upgrade package has an abnormality. If the upgrade package is complete and correct, start the software upgrade operation according to the established upgrade process. After the software upgrade is completed, report the upgrade results to the regional virtual server.

[0112] In one embodiment, the regional virtual server continuously broadcasts upgrade package information on the regional broadcast address according to a preset period. The broadcast information includes detailed information of the upgrade package, status information of the regional virtual server, and an upgrade request. The client node receives the broadcast information from the regional virtual server, parses the broadcast information, and extracts detailed information of the upgrade package and the upgrade request. The client node determines whether it needs to perform an upgrade operation based on the upgrade request.

[0113] The following describes the present application in detail from another perspective.

[0114] In the existing technology, client upgrades are heavily dependent on the central server status. Once the server fails, the entire system will fail to complete the upgrade. In this invention, each client is assigned to a different area by the operation and maintenance center, and each area recommends a virtual server to achieve distributed software upgrades.

[0115] Software upgrade deployment diagram as shown below Figure 2 shown.

[0116] The operation and maintenance personnel first configure the current system scale on the operation and maintenance server and pre-set the maximum capacity that the upgrade area can tolerate.

[0117] After each client device node is powered on, the upgrade module sends an online request to the operation and maintenance server, and then waits for the server to return the corresponding multicast address. The multicast address is used for communication between devices in the area.

[0118] The client upgrade module recommends server nodes in each region based on specific recommendation rules. For example, region 1 recommends node 3 as the server, and region 2 recommends node 8 as the server.

[0119] On the maintenance server side, maintenance personnel manually upload the upgrade package to the central upgrade module. At the same time, through the maintenance interface, maintenance personnel can monitor the system upgrade progress and any anomalies in real time.

[0120] The region partitioning algorithm is divided into two stages, as follows.

[0121] Phase 1 (prepare): The operation and maintenance personnel use the operation and maintenance server to set the current number of system nodes T and the maximum number of nodes in each area M. Based on the set parameters, the operation and maintenance server then calculates the total number of areas At the same time, the server will allocate a unique multicast address for each area in the address pool.

[0122] Phase 2 (distribute): When a device online request is received, the number of online nodes S will automatically increase, which will be used to calculate the partition index value of the device. When S is less than N, the system will partition the devices in the order they come online and notify the current node of the multicast address, while generating the optimal node array for the region. ,This array is used to store the comprehensive score of each node and the corresponding multicast address.

[0123] When S is greater than or equal to N, the system calculates The index value a of the current area is calculated. At this time, for the newly launched node, the system will compare its comprehensive score with the comprehensive scores of the nodes in the array R. If the comprehensive score of is lower than that of all nodes in R, the new node is notified to use the multicast address of area a; The comprehensive score of is better than some nodes in array R, then select the node with the lowest score from these nodes. , and notify the new node to use The multicast address of array R is replaced The comprehensive score of the node is , and swap the elements in the array and , to ensure that the array R can always reflect the optimal node situation in the current area, thereby effectively avoiding the problem of excessive performance gaps between regions and maintaining the efficient and stable operation of the entire system.

[0124] The regional server election algorithm uses a comprehensive scoring algorithm based on several factors, including current device load, remaining network bandwidth, packet loss rate, remaining disk capacity, and the number of past elections. Specifically, these factors are considered to calculate a score for each node device, and the node with the highest score is selected as the server node. During an election cycle, reelection will not be conducted unless network nodes change. This election mechanism ensures the stability of regional servers over a certain period of time while also allowing for flexible adjustments based on network conditions, ensuring efficient and stable system upgrades. The specific algorithm implementation is as follows.

[0125] Evaluation factor set: .

[0126] Given that server nodes are responsible for storing node information and software upgrade packages in the current area, in order to effectively avoid the large amount of memory operations caused by frequent node replacement and prevent unnecessary repeated downloads of software upgrade packages, when evaluating nodes, the number of times the node was elected in the past cycle has become one of the key and indispensable evaluation factors.

[0127] Factor weight set ,in, Representation factors The weight of .

[0128] Using Operators ,calculate Average value within a period, where k is a constant and represents the number of statistics within a statistical period.

[0129] Using Operators Calculate the number of times you were selected in the past statistical period.

[0130] Calculate the comprehensive score , where m is the critical value of the remaining disk capacity.

[0131] The flow chart of the election area server is as follows Figure 3 shown.

[0132] In step 101, after the regional assignment is complete, Client 1 and Client 2 each obtain their local operating system and software versions, calculate their comprehensive scores, and then broadcast information periodically using the regional multicast address assigned during regional assignment. During this process, only nodes within the regional multicast address range receive the broadcasted node information.

[0133] In step 102, after receiving the node information from client 1, client 2 stores client 1's operating system and software version numbers. It then compares the comprehensive scores of the remote node with its own node to determine whether its own node qualifies as a regional server for the current region. If the result is positive, it proceeds to the next step. If not, it does not perform any additional operations and continues to monitor data broadcast by other nodes.

[0134] Step 103: Client 2 reassembles the synchronization message of the regional multicast address, and adds the regional server identifier during the reassembly process to indicate its special role in the region.

[0135] In step 104, after receiving the multicast message from client 2 carrying the regional server identifier, client 1 compares itself with client 2 to determine whether it is more suitable to serve as the regional server. If client 1 believes it is more suitable, that is, it disagrees with client 2's identification, it sends a notification to client 2 stating that the regional server application failed. At the same time, it updates the regional multicast message to designate client 1 as the regional server. If client 1 believes client 2 is more suitable to serve as the regional server, it does nothing.

[0136] Step 105: After receiving the failure response message sent by client 1, client 2 immediately stops sending the regional server identifier on the regional multicast address and enters the receiving state to wait for subsequent related information.

[0137] In step 106, client 2, in the receiving state, initiates the scheduled link detection function after receiving the regional server broadcast request from client 1. During the detection process, if client 1 is detected as offline, the process repeats steps 104 and 105 to re-determine the regional server. If client 1 is not detected as offline, step 102 is continued to monitor the broadcast information of the regional multicast address.

[0138] Regional server upgrade process is as follows Figure 4 shown.

[0139] In step 201, the operation and maintenance personnel log in to the operation and maintenance server through a browser and upload the upgrade package to a designated location. After the upload is completed, the key information of the upgrade package is configured in detail in the central upgrade module, including the upgrade package version, applicable operating system type, and upgrade package download address.

[0140] In step 202, after completing the upgrade package configuration, the central upgrade module continuously and stably distributes the upgrade package information to all nodes in the network using the default multicast address as the transmission channel, according to a pre-set period. This periodic broadcast method ensures that all potential receiving nodes have the opportunity to obtain the latest upgrade package information and be informed of system upgrade status in a timely manner.

[0141] In step 203, upon receiving the upgrade request from the central upgrade module, the regional server, previously generated using specific recommendation rules, rapidly parses the request and retrieves detailed information about the upgrade package. Simultaneously, the regional server determines whether any nodes within its current region require a software upgrade based on the software version information stored for all neighboring nodes. If all nodes in the region are determined to be up-to-date and no upgrade is required, the regional server immediately provides feedback to the central upgrade module, informing it that the region already has the latest version and no upgrade is required. If any nodes require an upgrade, the regional server initiates a download request to the server address specified in the upgrade package information to retrieve the corresponding upgrade package.

[0142] In step 204, after the regional server successfully downloads the upgrade package, it immediately verifies the package's integrity using CRC (Cyclic Redundancy Check) (CRC) verification. CRC verification calculates the cyclic redundancy check (CRC) code of the upgrade package data and compares it with a preset checksum to determine whether the package suffered any anomalies, such as data loss or corruption, during transmission. If the verification result indicates an anomaly in the upgrade package, the regional server immediately notifies the central upgrade module of the anomaly. Upon receiving the notification, the central upgrade module aggregates all relevant anomaly information and reports it to the operations and maintenance center, enabling operations and maintenance personnel to promptly understand the situation and take appropriate remedial measures. If the verification result indicates the upgrade package is intact, the regional server stores the upgrade package in a designated local storage location and simultaneously updates the software version information carried in its periodic broadcast messages to ensure the latest software version information transmitted to other nodes.

[0143] In step 205, after the regional server completes storing the upgrade package and updating the software version information, it continuously broadcasts the latest software version information via the regional multicast address at a predetermined interval. Upon receiving this broadcast message, other node clients in the region determine whether their own software version requires an update based on the message content. They then officially enter the client upgrade process and begin their respective software upgrade operations.

[0144] Regional client upgrade process is as follows Figure 5 shown.

[0145] In step 301, the regional server continuously broadcasts the upgrade package information on the regional multicast address according to the system-set period. This information includes key data such as the upgrade package version number, applicable software version range, upgrade content summary, and download path.

[0146] In step 302, after receiving the upgrade request from the regional server, the client compares its current software version with the version specified in the upgrade package information to determine whether an update is required. If the comparison confirms that the client's current version is already the latest and no upgrade is required, the client sends a feedback message to the regional server, informing it that no upgrade is required. If the client determines that the current version requires an update, it initiates a download request to the server specified in the upgrade package information, obtaining the corresponding upgrade package.

[0147] In step 303, after the client successfully downloads the upgrade package, it immediately verifies its integrity using CRC verification. If the verification result indicates an anomaly in the upgrade package, the client immediately sends a notification to the regional server, informing it of the anomaly. If the verification result indicates the upgrade package is complete and correct, the client initiates the software upgrade according to the established upgrade process. After the software upgrade is complete, the client reports the upgrade results to the regional server.

[0148] In step 304, after receiving the upgrade results reported by each client, the regional server will regularly summarize and organize these results and report them to the operation and maintenance server at predetermined time intervals.

[0149] In step 305, the operations server monitors and analyzes the upgrade results of each node reported by the regional servers in real time. If any anomalies occur, the operations server notifies operations personnel for manual intervention. Based on the specific situation, operations personnel can take targeted measures to remotely diagnose and repair problematic clients, ensuring the smooth completion of the entire software upgrade process and maintaining stable system operation.

[0150] This application can be applied to distributed system software upgrades, resource synchronization and other fields.

[0151] This application has the following advantages.

[0152] 1. Using the regional division mechanism, reasonable zoning can be achieved based on a variety of factors.

[0153] 2. A cluster head selection algorithm that comprehensively considers multiple factors ensures the selection of a suitable cluster head, and the upgrade pressure is distributed from the traditional central server to the regional servers.

[0154] 3. Regional servers can be recommended in real time. When the original server fails, a new server can be quickly recommended to avoid the inability to upgrade other devices in the system due to server failure.

[0155] 4. Each upgrade client reports the upgrade results in real time. Compared with traditional upgrade methods, it can accurately locate abnormal devices and reduce labor and time costs.

[0156] 5. A dynamic, adaptive election strategy is employed to periodically monitor cluster head node activity and stress parameters, enabling real-time health assessment of cluster head nodes. When node performance degradation or overload is detected, the system automatically triggers a re-election process, ensuring that the cluster head role remains with the optimal node.

[0157] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A distributed system software upgrade method, wherein the distributed system includes an operation and maintenance server and multiple client nodes; characterized in that: The multiple client nodes are respectively assigned to different regions, and the operation and maintenance server allocates a corresponding regional multicast address to each region in the address pool; the client nodes in each region jointly elect one of the client nodes as the regional virtual server through internal request interaction based on device resources and network status in the current cycle, and monitor the operating status of the regional virtual server in real time within a cycle. When the regional virtual server is abnormal, a new regional virtual server node is re-elected in the current region; The distributed system software upgrade method, applied to a regional virtual server, includes: Receive an upgrade request from the operation and maintenance server, parse the request content, and obtain the upgrade package information from it; at the same time, based on the software version information of all other client nodes stored in its own storage, determine whether all other client nodes in the current area need to upgrade their software; if no upgrade is required, feedback is sent to the operation and maintenance server, informing it that the local area has the latest version and no upgrade is required; if an upgrade is required, a download request is initiated to the server address specified in the upgrade package information to obtain the corresponding upgrade package; the upgrade package information includes the upgrade package version number, applicable software version range, upgrade content summary, and download path; After successfully downloading the upgrade package, the integrity of the current upgrade package is verified. If there is any anomaly in the upgrade package, the operation and maintenance server is notified of the anomaly. If the upgrade package is complete and correct, the upgrade package is stored in the designated local storage location. At the same time, the software version information carried in its own periodic broadcast message is updated to ensure that the software version information transmitted to other client nodes in the area is the latest state. After completing the storage of the upgrade package and updating the software version information, the latest software version information is continuously sent through the regional multicast address according to the established period; The multiple client nodes are respectively classified into different areas, specifically including: Preset the number of nodes T in the current distributed system and the maximum number of nodes M in each region; based on the number of nodes T and the maximum number of nodes M, the operation and maintenance server calculates the total number of regions At the same time, the operation and maintenance server allocates a unique multicast address to each area in the address pool; When the operation and maintenance server receives an online request from any client node, the number of online nodes S will automatically increase, which will be used to calculate the partition index value of the client node in the future. When S is less than N, the operation and maintenance server will partition the client nodes in the order in which they come online and notify the current node of the multicast address to generate the optimal node array in the region. ,This array is used to store the comprehensive score of each node and the corresponding multicast address; When S is greater than or equal to N, the operation and maintenance server uses the formula Calculate the index value a of the initial assigned area corresponding to the current client node; then, for the newly online client node, compare its comprehensive score with the existing nodes in the array R; if the new node If the comprehensive score of is lower than that of all nodes in R, the new node is notified to use the multicast address of area a; The comprehensive score of is higher than some nodes in array R, then select the node with the lowest score from these nodes. , and notify the new node to use The multicast address of array R is replaced The comprehensive score of the node is , and swap the elements in the array and , to ensure that the array R can always reflect the optimal node situation in the current area, thereby effectively avoiding the problem of large performance gaps between regions.

2. The distributed system software upgrade method according to claim 1, characterized in that: A comprehensive score is calculated based on the current device load, remaining network bandwidth, packet loss rate, remaining disk capacity, and the number of past selections. A corresponding score is calculated for each node device, and the node with the highest score is selected as the regional virtual server node. Specifically, it includes: The evaluation factor set is: ， Factor weight sets: ， in, Representation factors The weight of ; Using operators: ， calculate The average value within a period, where k is a constant and represents the number of statistics within a statistical period; Using operators: ， Calculate the result value of the number of times selected in the past statistical period; Calculate the comprehensive score: ， Where m represents the critical value of the remaining disk capacity.

3. The distributed system software upgrade method according to claim 2, characterized in that: Each region selects one of the client nodes as the regional virtual server in the current cycle, specifically including: S1: Any two client nodes in the region are recorded as the first client node and the second client node. After the first client node and the second client node complete the region allocation, they each obtain the operating system version and software version of the client node, calculate the comprehensive score of the client node, and broadcast it within the regional multicast address according to the established period; S2: After receiving the node information of the first client node, the second client node stores the operating system version and software version number of the first client node and compares the comprehensive score of the first client node with that of the second client node. The second client node determines whether the second client node is qualified to serve as a regional server for the current region based on the comprehensive score. If qualified, the second client node acts as a regional server and proceeds to the next step. Otherwise, no other operations are performed and the node continues to monitor the broadcast data of other client nodes. S3, when the second client acts as a regional server, reorganizes the synchronization message of the regional multicast address and adds the regional server identifier; S4. After receiving the multicast message from the second client node carrying the regional virtual server identifier, the first client node compares the client node with the second client node to determine whether the client node is more suitable to serve as the regional virtual server than the second client node. If the client node is more suitable, that is, the first client node disagrees with the identification of the second client node, and sends a notification to the second client that the application for the regional virtual server has failed. At the same time, the first client node updates the regional multicast message to designate the regional virtual server as the client node. If the second client node is suitable to serve as the regional virtual server, no action is taken. S5, when the second client node receives the regional virtual server application failure message sent by the first client node, the second client node immediately stops sending the regional server identifier on the regional multicast address, enters the receiving state, and waits for subsequent related information; S6, when the second client node is in the receiving state, after receiving the regional server request broadcast from the first client node, it starts the timed link detection function; during the detection process, if it is detected that the first client node is offline, the process of steps S2 to S5 is repeated, and the regional server is re-determined; if the second client node is not detected to be offline, it continues to monitor the broadcast information of the regional multicast address.

4. The distributed system software upgrade method according to claim 1, characterized in that: During an election cycle, unless the node serving as the region server changes, the node will not be re-elected as the region server.

5. The distributed system software upgrade method according to claim 1, characterized in that: The regional virtual server also includes: receiving the upgrade results reported by each client node in real time, summarizing and collating them regularly, and reporting them to the operation and maintenance server at predetermined time intervals.

6. The distributed system software upgrade method according to claim 5, characterized in that: The operation and maintenance server monitors and summarizes the upgrade results of each node reported by the regional server in real time. If an abnormality occurs, the operation and maintenance server notifies the operation and maintenance personnel to perform manual intervention.

7. The distributed system software upgrade method according to claim 1, characterized in that: Verifying the integrity of the current upgrade package includes: Use CRC check to verify the integrity of the current upgrade package: by calculating the cyclic redundancy check code of the upgrade package data and comparing it with the preset check value, it can be determined whether there is any abnormal situation of data loss or damage during the transmission of the upgrade package.

8. A distributed system software upgrade method, wherein the distributed system includes an operation and maintenance server and multiple client nodes; characterized in that: The multiple client nodes are respectively assigned to different regions, and the operation and maintenance server allocates a corresponding regional multicast address to each region in the address pool; the client nodes in each region jointly elect one of the client nodes as the regional virtual server through internal request interaction based on device resources and network status in the current cycle, and monitor the operating status of the regional virtual server in real time within a cycle. When the regional virtual server is abnormal, a new regional virtual server node is re-elected in the current region; The distributed system software upgrade method is applied to any other client node except for the regional virtual server, and includes: The regional virtual server continuously broadcasts the upgrade package information on the regional broadcast address according to a preset period; The client node receives the upgrade request from the regional virtual server and compares its current software version with the version specified in the upgrade package information to determine whether it needs to be upgraded. If not, it sends a feedback message to the regional virtual server to inform it that no upgrade is required. If an upgrade is required, it initiates a download request to the server based on the specified server address provided in the upgrade package information to obtain the corresponding upgrade package. After successfully downloading the upgrade package, the integrity of the upgrade package is verified. If there is any anomaly in the upgrade package, a notification is sent to the regional virtual server to inform it of the anomaly. If the upgrade package is complete and correct, the software upgrade operation is started according to the established upgrade process. After the software upgrade is completed, the upgrade results are reported to the regional virtual server. The multiple client nodes are respectively classified into different areas, specifically including: Preset the number of nodes T in the current distributed system and the maximum number of nodes M in each region; based on the number of nodes T and the maximum number of nodes M, the operation and maintenance server calculates the total number of regions At the same time, the operation and maintenance server allocates a unique multicast address to each area in the address pool; When the operation and maintenance server receives an online request from any client node, the number of online nodes S will automatically increase, which will be used to calculate the partition index value of the client node in the future. When S is less than N, the operation and maintenance server will partition the client nodes in the order in which they come online and notify the current node of the multicast address to generate the optimal node array in the region. ,This array is used to store the comprehensive score of each node and the corresponding multicast address; When S is greater than or equal to N, the operation and maintenance server uses the formula Calculate the index value a of the initial assigned area corresponding to the current client node; then, for the newly online client node, compare its comprehensive score with the existing nodes in the array R; if the new node If the comprehensive score of is lower than that of all nodes in R, the new node is notified to use the multicast address of area a; The comprehensive score of is higher than some nodes in array R, then select the node with the lowest score from these nodes. , and notify the new node to use The multicast address of array R is replaced The comprehensive score of the node is , and swap the elements in the array and , to ensure that the array R can always reflect the optimal node situation in the current area, thereby effectively avoiding the problem of large performance gaps between regions.

9. The distributed system software upgrade method according to claim 8, characterized in that: The regional virtual server continuously broadcasts the upgrade package information on the regional broadcast address according to a preset period, and the broadcast information includes detailed information of the upgrade package, status information of the regional virtual server and the upgrade request; The client node receives the broadcast information from the regional virtual server, parses the broadcast information, and extracts the detailed information of the upgrade package and the upgrade request; The client node determines whether it needs to perform an upgrade operation based on the upgrade request.

Images