Online degradation method, device, equipment, medium and product of transaction log module

Abstract

The application provides an online degradation method, device, equipment, medium and product of a transaction log module. The method is applied to a dual-control storage system which is redundant to each other, and comprises the following steps: detecting a transaction log module including a degradation identifier based on a preset detection period; performing process fault simulation, service logic service migration and version update operation on a local controller; if the local controller completes version update, performing process recovery operation on the local controller; after the process recovery of the local controller is completed, performing process fault simulation, service logic service migration and version update operation on a controller on the opposite side; and if the controller on the opposite side completes version update, performing process recovery operation on the controller on the opposite side. Thus, the online degradation of the transaction log module is realized, and the continuity and real-time performance of the service are ensured.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an online degradation method, apparatus, device, medium and product for a transaction log module. Background Technology

[0002] In a centralized, dual-controller redundant storage system, the transaction log module is a core component ensuring data persistence, data consistency, and fault recovery. The storage system's transaction log includes high and low versions: the low version uses fixed physical segments to manage data, resulting in limited scheduling flexibility; the high version introduces virtual segments for dynamic memory allocation, leading to higher resource utilization; when a high version has program logic defects, it needs to be downgraded to a low version to avoid operational risks.

[0003] Existing technologies often employ offline degradation solutions involving complete machine shutdown, service interruption for package replacement, and controller restart. However, these technologies result in long service interruption times, fail to guarantee the continuous operation of core services, and exhibit poor compatibility between high and low version log formats and memory structures, which can easily lead to log loss, data inconsistency, and even controller failure or system crashes, resulting in poor system usability and reliability.

[0004] Therefore, the existing downgrade solution has the problem of service interruption. Summary of the Invention

[0005] This application provides an online degradation method, apparatus, device, medium, and product for a transaction log module, in order to solve the problem of business interruption caused by the degradation of the transaction log module.

[0006] In a first aspect, embodiments of this application provide an online degradation method for a transaction log module, applied to a dual-controller storage system with redundant primary and backup modules, comprising:

[0007] Based on a preset detection cycle, check whether the transaction log module includes a degradation flag;

[0008] If included, process failure simulation is performed on the local controller, and the business logic services carried by the local controller are migrated to the counterpart controller.

[0009] Perform a version update operation on the local controller;

[0010] If the local controller completes the version update, then perform a process recovery operation on the local controller;

[0011] After the local controller process recovers, a process failure simulation is performed on the counterpart controller, and the business logic services carried by the counterpart controller are migrated to the local controller.

[0012] Perform a version update operation on the opposite controller;

[0013] If the counterpart controller completes a version update, then perform a process recovery operation on the counterpart controller.

[0014] In this solution, the dual-controller storage system detects transaction log degradation flags based on a preset detection cycle, and sequentially performs fault simulation, business logic service migration, and version update on the local controller and the remote controller. After the version update is completed, the corresponding process recovery operation is executed to achieve seamless online degradation of the transaction log module in the dual-controller storage system, ensuring business continuity during the online degradation process.

[0015] In one possible implementation, performing a version update operation on the local controller includes:

[0016] Based on a preset migration cycle, it checks whether all business logic services carried by the local controller have been migrated to the opposite controller.

[0017] If so, a memory structure conversion operation is performed on the local transaction log module; the local transaction log module refers to the transaction log module corresponding to the local controller; the memory structure conversion operation means converting the memory structure type of the transaction log module from a virtual segment with dynamically allocated memory units before the downgrade to a physical segment with fixed allocated memory units after the downgrade.

[0018] Obtain the virtual segments within the local transaction log module, mark the virtual segments, and obtain the virtual segments to be released;

[0019] Perform resource release operations on the virtual segment to be released;

[0020] Based on a preset release cycle, the release status of the virtual segment to be released is checked periodically;

[0021] If all release statuses are detected as complete, then the management structure quantity update operation is performed on the local transaction log module.

[0022] In this scheme, the migration of business logic services is detected. If the migration is complete, memory structure conversion, resource release, and management structure quantity updates are performed on the local controller to update its version. This ensures the local controller adapts to the degraded memory allocation mode, reclaims resources in an orderly manner, and avoids memory redundancy and structural chaos.

[0023] In one possible implementation, performing a resource release operation on the virtual segment to be released includes:

[0024] Obtain the access frequency and latest usage time of the virtual segment to be released;

[0025] Based on preset weight factors, access frequency, and latest usage time, the virtual segment to be released is weighted and calculated to obtain the weight value of the virtual segment to be released.

[0026] Based on the weight values, the virtual segments to be released are sorted to obtain the execution order list of the virtual segments to be released;

[0027] Based on the execution order list, resource release operations are performed on the virtual segments to be released.

[0028] In this solution, a multi-dimensional weighted sorting strategy is adopted to determine the release order of virtual segments by using preset weight factors, access frequency of virtual segments to be released, and latest usage time. This prioritizes the release of virtual segments with less impact on business, thereby improving resource release efficiency and reducing the impact on business.

[0029] In one possible implementation, after periodically detecting the release status of the virtual segment to be released based on a preset release cycle, the method further includes:

[0030] If a virtual segment to be released is detected as not yet released and the current detection time exceeds the preset timeout threshold, a rewrite operation is performed on the data in the virtual segment to be released. The rewrite operation refers to rewriting data that conforms to the virtual segment format into data that conforms to the physical segment format.

[0031] Store data that conforms to the physical segment format in the physical segment, and delete data that conforms to the virtual segment format;

[0032] Update the release status of the virtual segment to be released to "release complete" and synchronize the release status to the controller on the other side.

[0033] In this scheme, if there are virtual segments that have not been released after a timeout, the data in the virtual segments to be released is rewritten into physical segment format, the physical segment format data is stored in the physical segment and the original data is deleted, the release status is updated and synchronized to the other controller, so as to solve the problem of the virtual segments to be released getting stuck during the release process and ensure the consistency of log data status between the local controller and the other controller.

[0034] In one possible implementation, performing a management structure quantity update operation on the local transaction log module includes:

[0035] Obtain memory usage status data for the dual-controller storage system;

[0036] Based on memory usage status data, calculate the minimum number of management structures required for the degraded transaction log module;

[0037] Based on the minimum number of management structures, perform a management structure quantity update operation on the local transaction log module.

[0038] In this solution, the minimum number of management structures is calculated by using the memory usage status data of the dual-controller storage system, thereby achieving precise matching of memory resources, improving memory resource utilization, and reducing system overhead.

[0039] In one possible implementation, after performing a process recovery operation on the contra-side controller, the method further includes:

[0040] Based on the preset load distribution strategy, business migration scheduling is carried out until the dual-controller storage system reaches a load-balanced state.

[0041] In this solution, a preset load distribution strategy is used to migrate the business logic services carried by the counterpart controller back to the local controller, so as to achieve load balancing of the dual-controller storage system and ensure the reliability and stability of the system.

[0042] Secondly, embodiments of this application provide an online degradation device for a transaction log module, comprising:

[0043] The detection module is used to detect whether the transaction log module includes a degradation flag based on a preset detection period.

[0044] The first migration module is used, if applicable, to simulate process failures on the local controller and migrate the business logic services carried by the local controller to the counterpart controller.

[0045] The first update module is used to perform version update operations on the local controller;

[0046] The first recovery module is used to perform process recovery operations on the local controller if the local controller completes the version update.

[0047] The second migration module is used to simulate process failure of the counterpart controller after the local controller process is restored, and to migrate the business logic services carried by the counterpart controller to the local controller.

[0048] The second update module is used to perform version update operations on the counterpart controller.

[0049] The second recovery module is used to perform process recovery operations on the counterpart controller if the counterpart controller completes a version update.

[0050] In one possible implementation, the first update module is specifically used for:

[0051] Based on a preset migration cycle, it checks whether all business logic services carried by the local controller have been migrated to the opposite controller.

[0052] If so, a memory structure conversion operation is performed on the local transaction log module; the local transaction log module refers to the transaction log module corresponding to the local controller; the memory structure conversion operation means converting the memory structure type of the transaction log module from a virtual segment with dynamically allocated memory units before the downgrade to a physical segment with fixed allocated memory units after the downgrade.

[0053] Obtain the virtual segments within the local transaction log module, mark the virtual segments, and obtain the virtual segments to be released;

[0054] Perform resource release operations on the virtual segment to be released;

[0055] Based on a preset release cycle, the release status of the virtual segment to be released is checked periodically;

[0056] If all release statuses are detected as complete, then the management structure quantity update operation is performed on the local transaction log module.

[0057] In one possible implementation, the first update module is specifically used for:

[0058] Obtain the access frequency and latest usage time of the virtual segment to be released;

[0059] Based on preset weight factors, access frequency, and latest usage time, the virtual segment to be released is weighted and calculated to obtain the weight value of the virtual segment to be released.

[0060] Based on the weight values, the virtual segments to be released are sorted to obtain the execution order list of the virtual segments to be released;

[0061] Based on the execution order list, resource release operations are performed on the virtual segments to be released.

[0062] In one possible implementation, the first update module is specifically used for:

[0063] If a virtual segment to be released is detected as not yet released and the current detection time exceeds the preset timeout threshold, a rewrite operation is performed on the data in the virtual segment to be released. The rewrite operation refers to rewriting data that conforms to the virtual segment format into data that conforms to the physical segment format.

[0064] Store data that conforms to the physical segment format in the physical segment, and delete data that conforms to the virtual segment format;

[0065] Update the release status of the virtual segment to be released to "release complete" and synchronize the release status to the controller on the other side.

[0066] In one possible implementation, the first update module is specifically used for:

[0067] Obtain memory usage status data for the dual-controller storage system;

[0068] Based on memory usage status data, calculate the minimum number of management structures required for the degraded transaction log module;

[0069] Based on the minimum number of management structures, perform a management structure quantity update operation on the local transaction log module.

[0070] In one possible implementation, after performing a process recovery operation on the contra-side controller, the online degradation device of the transaction log module further includes a third migration module, which is specifically used for:

[0071] Based on the preset load distribution strategy, business migration scheduling is carried out until the dual-controller storage system reaches a load-balanced state.

[0072] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0073] The memory stores instructions that the computer executes;

[0074] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0075] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0076] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0077] The online degradation method, apparatus, device, medium, and product for the transaction log module provided in this application embodiment, in a dual-controller storage system with redundant primary and backup, detects whether the transaction log module includes a degradation identifier based on a preset detection period. If it does, a process failure simulation is performed on the local controller, and the business logic services carried by the local controller are migrated to the counterpart controller. A version update operation is performed on the local controller. If the local controller completes the version update, a process recovery operation is performed on the local controller. After the local controller process recovery is completed, a process failure simulation is performed on the counterpart controller, and the business logic services carried by the counterpart controller are migrated to the local controller. A version update operation is performed on the counterpart controller. If the counterpart controller completes the version update, a process recovery operation is performed on the counterpart controller. This ensures business continuity during the online degradation of the transaction log module. In the above method, the dual-controller storage system periodically detects the degradation identifier of the transaction log module and sequentially performs process failure simulation, business logic service migration, version update, and process recovery on the local controller and the counterpart controller. Compared with the traditional whole-machine shutdown upgrade mode, the method of this application avoids the problems of business interruption during single-controller update and disordered update sequence in dual-controller systems. The system enables seamless online degradation updates of the transaction log module, ensuring uninterrupted business operations and improving system continuity. Attached Figure Description

[0078] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0079] Figure 1 A flowchart illustrating an online degradation method for a transaction log module provided in this application embodiment. Figure 1 ;

[0080] Figure 2 A flowchart illustrating an online degradation method for a transaction log module provided in this application embodiment. Figure 2 ;

[0081] Figure 3 This is a schematic diagram of the memory structure provided in an embodiment of this application;

[0082] Figure 4 A schematic diagram illustrating the process of a dual-controller storage system performing a version update operation, as provided in an embodiment of this application.

[0083] Figure 5 A schematic diagram of the structure of an online degradation device for a transaction log module provided in an embodiment of this application;

[0084] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0085] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0086] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0087] In centralized storage systems, the transaction log module serves as a core foundational service, playing a crucial role in ensuring data persistence and system failure recovery. When the storage system performs data write operations, it typically needs to commit the data to the transaction log first, and then asynchronously write it to the cache or disk to improve system performance.

[0088] In this process, the memory structure design of the transaction log directly affects data storage efficiency and system stability. For example, older software versions use fixed-size physical segments to manage log data, while newer software versions use virtual segments to achieve more flexible resource allocation. However, when problems occur in the newer software version, it is necessary to downgrade to the older version to mitigate the risks.

[0089] Existing offline downgrade methods require a complete halt to storage services, replacement of software packages, and a system restart, resulting in prolonged business interruptions that may impact the continuity of critical business operations. This fails to meet the downgrade requirements of scenarios with extremely high business continuity demands (such as financial transactions or scientific computing). Furthermore, differences in memory structure between high-version and low-version transaction logs (e.g., the management mechanisms of virtual and physical segments) can lead to data compatibility issues. During offline downgrade, failure to release high-version virtual segments may result in residual memory resources. After restarting, the low-version system may not correctly identify this residual data, leading to data loss or system anomalies. Moreover, existing technologies lack a version adaptation mechanism for the transaction log module, preventing high-version data from being effectively processed by the low-version system after downgrade, further limiting the feasibility and security of downgrade operations.

[0090] Based on the above-mentioned technical problems, the technical concept of the embodiments of this application is as follows:

[0091] Based on a preset detection cycle, the system checks whether the transaction log module includes a degradation flag. If so, it simulates a process failure on the local controller and migrates the business logic services hosted on the local controller to the peer controller. It then performs a version update on the local controller. If the local controller completes the version update, it performs a process recovery operation. After the local controller process recovery is complete, it simulates a process failure on the peer controller and migrates the business logic services hosted on the peer controller to the local controller. It then performs a version update on the peer controller. If the peer controller completes the version update, it performs a process recovery operation. After the peer controller process recovery is complete, it performs business migration scheduling until the dual-controller storage system reaches a load-balanced state, ensuring business continuity during online degradation of the transaction log module. In this method, the dual-controller storage system periodically checks the degradation flag of the transaction log module and sequentially performs process failure simulation, business logic service migration, version update, and process recovery on both the local and peer controllers. This avoids the problems of business interruption during single-controller updates or disordered update sequences during dual-controller updates. The system enables seamless online degradation updates of the transaction log module, improving business continuity and system reliability to meet the operational needs of high-reliability scenarios.

[0092] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0093] Figure 1 A flowchart illustrating an online degradation method for a transaction log module provided in this application embodiment. Figure 1 This method is applied to dual-controller storage systems with redundant primary and backup controllers, such as... Figure 1 As shown, the method includes:

[0094] S101. Based on the preset detection cycle, detect whether the transaction log module includes a degradation flag.

[0095] The degradation flag refers to the status flag bit or flag field in the transaction log module, which is used to trigger the online degradation process.

[0096] For example, the preset detection period can be 1 to 5 seconds.

[0097] In some embodiments, before detecting whether the transaction log module includes a degradation flag based on a preset detection period, the method further includes:

[0098] In response to user downgrade requests, generate downgrade preprocessing instructions for the transaction log module.

[0099] Based on the degradation preprocessing instructions, degradation identifier pairs are generated; the degradation identifier pairs are used to characterize the online degradation order of the transaction log modules of the local controller and the counterpart controller.

[0100] Based on the degradation flag pairs, add corresponding degradation flags to the transaction log modules of the local controller and the counterpart controller respectively.

[0101] User downgrade requests refer to online downgrade requests for the transaction log module issued by operations or management personnel.

[0102] Degradation preprocessing instructions refer to the executable control instructions generated by the management interface of a dual-controller storage system based on the user's degradation request after receiving the request.

[0103] Degradation identifier pairs refer to identifier combinations configured in pairs that define the order in which transaction log modules in a dual-controller storage system are degraded, including the degradation identifier configured on the local controller and the degradation identifier configured on the other controller.

[0104] Specifically, the management interface receives user downgrade requests and generates downgrade preprocessing instructions based on these requests. At this point, each business logic service senses the downgrade preprocessing instructions via a timer, causing the underlying functional submodules that the transaction log module depends on and are associated with to asynchronously execute downgrade preprocessing tasks. This ensures that the ongoing business logic service clears the high-version data before downgrade and generates the low-version data after downgrade through new business processes. The downgrade preprocessing task has no time limit and a duration of 30 minutes.

[0105] Furthermore, after all the underlying functional sub-modules have completed the degradation preprocessing tasks, the management interface generates corresponding degradation identifier pairs based on the degradation preprocessing instructions, and adds degradation identifiers to the transaction log module that is to perform online degradation operations.

[0106] S102. If included, then process failure simulation is performed on the local controller, and the business logic services carried by the local controller are migrated to the counterpart controller.

[0107] Process failure simulation refers to marking a business logic service as unavailable to suspend the process's external business scheduling and pre-log processing.

[0108] Specifically, after simulating process failure on the local controller, the primary / backup switch and service routing switch of the dual-controller storage system are triggered, thereby automatically migrating the business logic services carried by the local controller to the other controller without the upper-layer business being aware of it.

[0109] S103, Perform a version update operation on the local controller.

[0110] Version update operation refers to the operation of switching the transaction log module from the currently running high version to a low version. This includes switching the running version of the transaction log module, loading the downgraded low version program, converting the memory structure, releasing idle resources, and updating the number of management structures.

[0111] S104. If the local controller completes the version update, perform a process recovery operation on the local controller.

[0112] Process recovery operation refers to restarting and restoring unavailable business logic services and transaction log processes to normal operation after the version update operation is completed.

[0113] S105. After the local controller process is restored, perform process failure simulation on the counterpart controller and migrate the business logic services carried by the counterpart controller to the local controller.

[0114] Specifically, after the local controller process recovers, the business logic services carried on the remote controller are marked as unavailable, and the process's external business scheduling and pre-log processing operations are suspended. After simulating a process failure on the remote controller, the primary / backup switch and business routing switch of the dual-controller storage system are triggered. Without the upper-layer business being aware, the business logic services carried on the remote controller are automatically migrated to the local controller.

[0115] S106. Perform a version update operation on the opposite controller.

[0116] Specifically, the transaction log module corresponding to the counterpart controller is switched from the currently running high version to a low version. This includes switching the running version of the transaction log module corresponding to the counterpart controller, loading the downgraded low version program, converting the memory structure, releasing idle resources, and updating the number of management structures.

[0117] S107. If the counterpart controller completes the version update, then perform a process recovery operation on the counterpart controller.

[0118] Specifically, after the counterpart controller completes the version update operation, the business logic services and transaction log processes that were in an unavailable state in the counterpart controller will be restarted and restored to normal service status.

[0119] In some embodiments, after performing a process recovery operation on the contra-side controller, the method further includes:

[0120] Based on the preset load distribution strategy, business migration scheduling is carried out until the dual-controller storage system reaches a load-balanced state.

[0121] Business migration scheduling refers to the operation of reallocating the nodes that carry business logic services after both controllers have completed the online degradation of the transaction log module and process recovery.

[0122] For example, a preset load balancing strategy can be used to allow both the local controller and the remote controller to carry 50% of the business logic services.

[0123] Specifically, based on the load distribution strategy preset by the dual-controller storage system, the business logic services currently carried by the local controller are gradually and smoothly migrated back to the other controller, balancing the business processing pressure, log read and write load and memory resource usage of the two controllers, and ultimately maintaining the overall operation of the dual-controller storage system in a stable state of load balance.

[0124] The beneficial effects of this application's embodiments are as follows: In this embodiment, the degradation flag of the transaction log module is detected based on a preset detection period. The degradation flag is generated by the dual-controller storage system in response to the user's degradation request. The degradation preprocessing instruction and the degradation flag are then configured to the local and remote controllers respectively. At the same time, the underlying sub-module preprocessing is completed asynchronously, the high-version existing data is cleared, and low-version business data is generated. When the degradation flag is detected, the process failure simulation is first performed on the local controller, triggering the primary / backup and business routing switch, and the business is smoothly migrated to the remote controller. Then, the version degradation is performed on the local controller, and the process is restored after the program loading, memory structure conversion, and resource release are completed. Subsequently, the same logic is used to perform business migration, version update, and process recovery on the remote controller in sequence. After both controllers have completed degradation and process recovery, business migration scheduling is carried out according to the preset load distribution strategy to balance the dual-controller business processing, log reading and writing, and memory resource usage, so that the dual-controller storage system achieves a load-balanced steady state. The above method eliminates the need for system shutdown and restart. It achieves online lossless degradation by relying on alternating operation and maintenance of dual controllers and seamless business migration, effectively shortening business interruption time, ensuring the continuous operation of critical businesses, and optimizing system resource allocation to improve the stability and high availability of the dual-controller storage system.

[0125] exist Figure 1 Based on the embodiments, the following is combined Figure 2 The following provides a detailed explanation of "performing a version update operation on the local controller" in step S103 above.

[0126] Figure 2 A flowchart illustrating an online degradation method for a transaction log module provided in this application embodiment. Figure 2 ,like Figure 1 As shown, the method includes:

[0127] S201. Based on a preset migration cycle, detect whether all business logic services carried by the local controller have been migrated to the opposite controller.

[0128] For example, the preset migration period can be 2 seconds.

[0129] Specifically, every 2 seconds, the system iterates through the list of all business logic services on the local controller, verifies the service running identifier and business routing entries, and determines whether all services have been switched and scheduled to be carried by the opposite controller, with no residual local business instances.

[0130] S202. If so, then perform a memory structure conversion operation on the local transaction log module; the local transaction log module refers to the transaction log module corresponding to the local controller; the memory structure conversion operation means converting the memory structure type of the transaction log module from a virtual segment with dynamically allocated memory units before the downgrade to a physical segment with fixed allocated memory units after the downgrade.

[0131] The memory structure conversion operation refers to converting the memory structure type of the transaction log module from a virtual segment with dynamically allocated memory units before downgrading to a physical segment with fixed allocated memory units after downgrading. It is the core adaptation operation of the transaction log module downgrading and is used to complete the memory management mode switch.

[0132] Virtual segments refer to the log memory structure before degradation, which can dynamically request and flexibly allocate memory units as needed.

[0133] The physical segment refers to the degraded log memory structure, which requires pre-defined fixed memory units, static allocation, and no further dynamic expansion.

[0134] For example, such as Figure 3 As shown, when running version V1, the physical segment size in the power-saving memory is 1MB, corresponding to one transaction log instance, and the maximum number of physical segments per transaction log module is 10. When running version V2, in the power-saving memory, the virtual segment manager divides a physical segment into 8 virtual segments, each virtual segment being 128KB in size, and the maximum number of virtual segments per transaction log module is 255. One virtual segment belongs to one transaction log instance, while the 8 virtual segments divided from the same physical segment can be assigned to multiple different transaction log instances under the same business logic service (e.g., transaction log instance 1, transaction log instance 2, and transaction log instance 3).

[0135] Specifically, the virtual segment manager pre-allocates multiple virtual segments for reuse. When a transaction log instance requests a virtual segment from the virtual segment manager, the virtual segment manager allocates a virtual segment to the corresponding transaction log instance.

[0136] It is understood that V1 and V2 are identifiers for lower and higher versions, respectively, and are only used as examples and do not constitute a limitation on the specific running version.

[0137] S203. Obtain the virtual segments in the local transaction log module, mark the virtual segments, and obtain the virtual segments to be released.

[0138] Tagging refers to adding a mark to be released to virtual segments that are recyclable and have no real-time business read / write dependency.

[0139] Virtual segments awaiting release refer to virtual segments that have been marked and determined to meet the release conditions and can be recycled as idle resources.

[0140] Specifically, it iterates through all created virtual segments in the transaction log module corresponding to the local controller, filters out in-use virtual segments that still have business read / write sessions and log transactions that have not been committed, marks virtual segments that are idle, historically archived, or have no business dependencies, obtains virtual segments to be released, and summarizes all virtual segments to be released into a list of virtual segments to be released.

[0141] S204. Perform resource release operation on the virtual segment to be released.

[0142] In some embodiments, performing a resource release operation on the virtual segment to be released includes:

[0143] Get the access frequency and latest usage time of the virtual segment to be released.

[0144] Based on preset weight factors, access frequency, and latest usage time, the virtual segment to be released is weighted and calculated to obtain the weight value of the virtual segment to be released.

[0145] Based on the weight values, the virtual segments to be released are sorted to obtain the execution order table of the virtual segments to be released.

[0146] Based on the execution order list, resource release operations are performed on the virtual segments to be released.

[0147] Resource release operations refer to the operations of reclaiming the memory space occupied by virtual segments to be released, unregistering management entries, and releasing system resources.

[0148] Access frequency refers to the number of times a virtual segment is read, written, or accessed by the transaction log instance per unit of time.

[0149] The latest usage time refers to the timestamp of the last time the virtual segment was accessed, written to, or read by a business.

[0150] The weighting factor is a fixed configuration coefficient preset by the dual-controller storage system, used to balance the weight ratio of access frequency and usage time.

[0151] The execution order table refers to the sequence of virtual segment resource releases determined by sorting them according to their weight values.

[0152] For example, the access frequency and last access time of each virtual segment to be released in the past 5 minutes are collected, the access frequency is configured to be 0.6 and the weight factor of the latest usage time is configured to be 0.4, and a weighted calculation is performed to obtain the weight value corresponding to the virtual segment to be released. An execution order table is generated in ascending order of weight, and the virtual segment management structure is unregistered and the occupied memory pages are released in turn.

[0153] S205. Based on a preset release cycle, periodically detect the release status of the virtual segment to be released.

[0154] The release cycle refers to the preset timed polling interval, used to check the progress of virtual segment resource reclamation.

[0155] The release status refers to the indicator used to determine whether the virtual segment has completed memory reclamation and entry cancellation, including not yet released and released completely.

[0156] Specifically, based on a preset release cycle, a timer is used to cyclically detect whether all virtual segments to be released have been released. If all virtual segments to be released have been released, then step S206 is executed.

[0157] In some embodiments, after periodically detecting the release status of the virtual segment to be released based on a preset release period, the method further includes:

[0158] If a virtual segment to be released is detected as not yet released and the current detection time exceeds the preset timeout threshold, a rewrite operation is performed on the data in the virtual segment to be released. The rewrite operation refers to rewriting data that conforms to the virtual segment format into data that conforms to the physical segment format.

[0159] Data that conforms to the physical segment format is stored in the physical segment, and data that conforms to the virtual segment format is deleted.

[0160] Update the release status of the virtual segment to be released to "release complete" and synchronize the release status to the controller on the other side.

[0161] The timeout threshold refers to the preset maximum waiting time. If the current detection time exceeds the preset timeout threshold, the virtual segment release is determined to be stuck.

[0162] Data rewriting refers to the process of converting the format of log data stored in the virtual segment and rearranging it to adapt to the physical segment storage format.

[0163] For example, the preset release period is 3 seconds and the timeout threshold is 10 minutes. The release status of all virtual segments to be released is polled every 3 seconds. If there are virtual segments that have not been released after more than 10 minutes, a data rewrite operation is triggered to convert the variable-length format log data of the virtual segment into the fixed-length storage format of the physical segment. After writing the data into the physical segment, the original virtual segment data is deleted, and the release status is synchronized to the controller on the other side.

[0164] S206. If all release statuses are detected as complete, then perform a management structure quantity update operation on the local transaction log module.

[0165] In some embodiments, performing a management structure quantity update operation on the local transaction log module includes:

[0166] Obtain memory usage status data for the dual-controller storage system.

[0167] Based on memory usage data, calculate the minimum number of management structures required for the degraded transaction log module.

[0168] Based on the minimum number of management structures, perform a management structure quantity update operation on the local transaction log module.

[0169] Memory usage status data includes the overall memory usage rate of the dual-controller storage system, occupied memory, free memory, available memory, and the number of transaction log instances.

[0170] The minimum number of management structures refers to the minimum number of management structures required to adapt to the physical segment's operating mode after degradation and ensure normal log reading and writing.

[0171] The management structure quantity update operation refers to adjusting the configuration quantity of management entries, control blocks, and index structures within the transaction log according to the calculation results.

[0172] For example, the maximum number of management structures corresponding to a virtual segment is 255, and the maximum number of management structures corresponding to a physical segment is 40.

[0173] Specifically, a flexible adjustment mechanism is introduced when updating the number of management structures. The dual-controller storage system dynamically calculates the minimum number of management structures required for compatibility with lower versions based on current memory usage data (such as available memory size and the number of transaction log instances), and allows temporary expansion or contraction of management structures at runtime as needed. For example, if memory resources are sufficient, some redundant management structures can be retained to cope with sudden loads.

[0174] For example, the number of reserved management structures can be changed from 255 to 40.

[0175] Furthermore, after performing the management structure quantity update operation on the local transaction log module, the following operation is performed on the counterpart controller:

[0176] Based on a preset migration cycle, it checks whether all business logic services carried by the counterpart controller have been migrated to the local controller.

[0177] The counterpart transaction log module refers to the transaction log module corresponding to the counterpart controller.

[0178] For example, the preset migration period can be 2 seconds. Every 2 seconds, the system traverses the list of all business logic services on the other side controller, verifies the service running identifier and business routing entries, and determines whether all services have been switched and scheduled to be carried by the local controller, with no residual business instances on the other side.

[0179] If so, then perform a memory structure conversion operation on the opposite transaction log module.

[0180] Obtain the virtual segments within the counterparty's transaction log module, mark the virtual segments, and obtain the virtual segments to be released.

[0181] Iterate through all created virtual segments in the transaction log module corresponding to the counterpart controller, filter out in-use virtual segments that still have business read / write sessions and log transactions that have not been committed, mark virtual segments that are idle, historically archived, or have no business dependencies, obtain virtual segments to be released, and summarize all virtual segments to be released into a list of virtual segments to be released.

[0182] Perform resource release operations on the virtual segment to be released.

[0183] In some embodiments, performing a resource release operation on the virtual segment to be released includes:

[0184] Get the access frequency and latest usage time of the virtual segment to be released.

[0185] Based on preset weight factors, access frequency, and latest usage time, the virtual segment to be released is weighted and calculated to obtain the weight value of the virtual segment to be released.

[0186] Based on the weight values, the virtual segments to be released are sorted to obtain the execution order table of the virtual segments to be released.

[0187] Based on the execution order list, resource release operations are performed on the virtual segments to be released.

[0188] For example, the access frequency and last access time of each virtual segment to be released in the past 5 minutes are collected, the access frequency is configured to be 0.6 and the weight factor of the latest usage time is configured to be 0.4, and a weighted calculation is performed to obtain the weight value corresponding to the virtual segment to be released. An execution order table is generated in ascending order of weight, and the virtual segment management structure is unregistered and the occupied memory pages are released in turn.

[0189] Based on a preset release cycle, the release status of the virtual segment to be released is checked periodically.

[0190] Based on a preset release cycle, a timer is used to cyclically check whether all virtual segments to be released have been fully released. If a virtual segment to be released is detected as not fully released and the current detection time exceeds a preset timeout threshold, the data in the virtual segment to be released is rewritten. Data conforming to the physical segment format is stored in the physical segment, and data conforming to the virtual segment format is deleted. The release status of the virtual segment to be released is updated to release complete, and the release status is synchronized to the local controller.

[0191] For example, the preset release period is 3 seconds and the timeout threshold is 10 minutes. The release status of all virtual segments to be released is polled every 3 seconds. If there are virtual segments that have not been released after more than 10 minutes, a data rewrite operation is triggered to convert the variable-length format log data of the virtual segment into the fixed-length storage format of the physical segment. After writing the data into the physical segment, the original virtual segment data is deleted, and the release status is synchronized to the local controller.

[0192] If all release statuses are detected as complete, then perform a management structure quantity update operation on the opposite transaction log module.

[0193] In some embodiments, performing a management structure quantity update operation on the counterparty transaction log module includes:

[0194] Obtain memory usage status data for the dual-controller storage system.

[0195] Based on memory usage data, calculate the minimum number of management structures required for the degraded transaction log module.

[0196] Based on the minimum number of management structures, perform a management structure quantity update operation on the opposite transaction log module.

[0197] Specifically, a flexible adjustment mechanism is introduced when updating the number of management structures. The dual-controller storage system dynamically calculates the minimum number of management structures required for compatibility with lower versions based on current memory usage data (such as available memory size and the number of transaction log instances), and allows temporary expansion or contraction of management structures at runtime as needed. For example, if memory resources are sufficient, some redundant management structures can be retained to cope with sudden loads.

[0198] For example, the number of reserved management structures can be changed from 255 to 40.

[0199] In some embodiments, such as Figure 4 As shown, before the dual-controller storage system performs online degradation, the management interface issues degradation preprocessing instructions. Each business logic service module senses the degradation preprocessing instructions through a timer and executes the degradation preprocessing tasks asynchronously until all business logic services complete the degradation preprocessing tasks. Among them, after the transaction log module senses the degradation preprocessing instructions through a timer, the corresponding degradation preprocessing task is to configure the corresponding degradation identifier.

[0200] After all business logic services have completed the degradation preprocessing tasks, if both Control 0 and Control 1 are currently running at version V2, then process failure simulation is performed on Control 0, and the business logic services of Control 0 are migrated to Control 1. A version update operation is performed on Control 0 to convert Control 0 from version V2 to version V1. Similarly, process failure simulation is performed on Control 1, and the business logic services of Control 1 are migrated to Control 0. A version update operation is performed on Control 1 to convert Control 1 from version V2 to version V1.

[0201] It is understood that Control 0 and Control 1 are identifiers for the local controller and the remote controller, respectively, and are merely illustrative references and do not constitute a limitation on any specific controller.

[0202] The beneficial effects of this application's embodiments are as follows: In this application's embodiments, based on a preset migration cycle polling detection, after confirming that the local controller's business logic services have been fully migrated to the counterpart controller, the transaction log module's memory structure is converted, switching the dynamically allocated virtual segment memory structure before degradation to a fixed statically allocated physical segment memory structure after degradation. All virtual segments are traversed, filtering out those still having business read / write dependencies, marking idle archives and virtual segments without business dependencies, and selecting virtual segments to be released. Then, weight values ​​are calculated based on access frequency, latest usage time, and preset weight factors, and the release order is determined by sorting by weight, sequentially reclaiming memory space and deregistering management entries. The release status is checked periodically based on a preset release cycle. If a virtual segment release times out and becomes stuck, the virtual segment log data is rewritten into physical segment format and stored in the database, and the release status is synchronously updated to the counterpart controller. After all virtual segments are released, memory usage status data of the dual-controller storage system is collected, the minimum number of management structures adapted to the degradation mode is dynamically calculated, and the number of management structures in the transaction log module is elastically updated. The dual-controller system uses the same alternating execution logic to complete version updates. Before downgrading, the system can issue preprocessing instructions through the management interface. Each business module asynchronously completes preprocessing and configures downgrading flags, enabling smooth online downgrading of the dual-controller system from a higher version to a lower version. In this method, structured memory switching between virtual and physical segments standardizes memory allocation rules after downgrading, avoiding dynamic memory fragmentation and disordered resource occupation. A weighted sorting reclamation mechanism improves the rationality and efficiency of idle memory release, reducing resource waste. Added timeout data rewriting fault-tolerant logic solves the problem of virtual segment release deadlock, significantly improving the stability and fault tolerance of the online downgrading process. The number of management structures is flexibly adjusted based on memory status to adapt to the operating requirements of lower versions, balancing resource saving and adaptability to sudden business loads. The dual controllers synchronously reuse standardized version update processes, enabling seamless business migration without downtime or restart, ensuring continuous operation of storage services and significantly improving the automation, reliability, and operational adaptability of the online downgrading of the transaction log module in the dual-controller storage system.

[0203] Figure 5 This is a schematic diagram of the structure of an online degradation device for a transaction log module provided in an embodiment of this application, as shown below. Figure 5 As shown, the online degradation device of the transaction log module includes a detection module 501, a first migration module 502, a first update module 503, a first recovery module 504, a second migration module 505, a second update module 506, and a second recovery module 507.

[0204] The detection module 501 is used to detect whether the transaction log module includes a degradation flag based on a preset detection period.

[0205] The first migration module 502 is used, if included, to simulate process failures on the local controller and migrate the business logic services carried by the local controller to the counterpart controller.

[0206] The first update module 503 is used to perform version update operations on the local controller.

[0207] The first recovery module 504 is used to perform a process recovery operation on the local controller if the local controller completes a version update.

[0208] The second migration module 505 is used to simulate process failure on the counterpart controller after the local controller process has recovered, and to migrate the business logic services carried by the counterpart controller to the local controller.

[0209] The second update module 506 is used to perform a version update operation on the counterpart controller.

[0210] The second recovery module 507 is used to perform a process recovery operation on the counterpart controller if the counterpart controller completes a version update.

[0211] In some embodiments, the first update module 503 is specifically used for:

[0212] Based on a preset migration cycle, it checks whether all business logic services carried by the local controller have been migrated to the opposite controller.

[0213] If so, a memory structure conversion operation is performed on the local transaction log module; the local transaction log module refers to the transaction log module corresponding to the local controller; the memory structure conversion operation means converting the memory structure type of the transaction log module from a virtual segment with dynamically allocated memory units before the downgrade to a physical segment with fixed allocated memory units after the downgrade.

[0214] Obtain the virtual segments within the local transaction log module, mark the virtual segments, and obtain the virtual segments to be released;

[0215] Perform resource release operations on the virtual segment to be released;

[0216] Based on a preset release cycle, the release status of the virtual segment to be released is checked periodically;

[0217] If all release statuses are detected as complete, then the management structure quantity update operation is performed on the local transaction log module.

[0218] In some embodiments, the first update module 503 is specifically used for:

[0219] Obtain the access frequency and latest usage time of the virtual segment to be released;

[0220] Based on preset weight factors, access frequency, and latest usage time, the virtual segment to be released is weighted and calculated to obtain the weight value of the virtual segment to be released.

[0221] Based on the weight values, the virtual segments to be released are sorted to obtain the execution order list of the virtual segments to be released;

[0222] Based on the execution order list, resource release operations are performed on the virtual segments to be released.

[0223] In some embodiments, the first update module 503 is specifically used for:

[0224] If a virtual segment to be released is detected as not yet released and the current detection time exceeds the preset timeout threshold, a rewrite operation is performed on the data in the virtual segment to be released. The rewrite operation refers to rewriting data that conforms to the virtual segment format into data that conforms to the physical segment format.

[0225] Store data that conforms to the physical segment format in the physical segment, and delete data that conforms to the virtual segment format;

[0226] Update the release status of the virtual segment to be released to "release complete" and synchronize the release status to the controller on the other side.

[0227] In some embodiments, the first update module 503 is specifically used for:

[0228] Obtain memory usage status data for the dual-controller storage system;

[0229] Based on memory usage status data, calculate the minimum number of management structures required for the degraded transaction log module;

[0230] Based on the minimum number of management structures, perform a management structure quantity update operation on the local transaction log module.

[0231] In some embodiments, after performing a process recovery operation on the counterpart controller, the online degradation device of the transaction log module further includes a third migration module, which is specifically used for:

[0232] Based on the preset load distribution strategy, business migration scheduling is carried out until the dual-controller storage system reaches a load-balanced state.

[0233] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 6 As shown, the electronic device provided in this embodiment includes at least one processor 601 and a memory 602. Optionally, the electronic device further includes a communication component 603. The processor 601, memory 602, and communication component 603 are connected via a bus 604.

[0234] In a specific implementation, at least one processor 601 executes computer execution instructions stored in memory 602, causing at least one processor 601 to perform the above-described method.

[0235] The specific implementation process of processor 601 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0236] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0237] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0238] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0239] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the technical solutions provided in any of the foregoing method embodiments.

[0240] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions provided in the foregoing method embodiments.

[0241] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0242] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0243] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0244] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or as software program modules.

[0245] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0246] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0247] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0248] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0249] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. An online degradation method for a transaction log module, characterized in that, Applications include dual-controller storage systems with redundant primary and backup configurations, including: Based on a preset detection cycle, check whether the transaction log module includes a degradation flag; If included, process failure simulation is performed on the local controller, and the business logic services carried by the local controller are migrated to the counterpart controller. Perform a version update operation on the local controller; If the local controller completes the version update, then perform a process recovery operation on the local controller; After the local controller process recovers, a process failure simulation is performed on the counterpart controller, and the business logic services carried by the counterpart controller are migrated to the local controller. Perform a version update operation on the contra-side controller; If the counterpart controller completes a version update, then a process recovery operation is performed on the counterpart controller.

2. The method according to claim 1, characterized in that, The step of performing a version update operation on the local controller includes: Based on a preset migration cycle, it is detected whether all business logic services carried by the local controller have been migrated to the opposite controller. If so, a memory structure conversion operation is performed on the local transaction log module; the local transaction log module refers to the transaction log module corresponding to the local controller; the memory structure conversion operation refers to converting the memory structure type of the transaction log module from a virtual segment with dynamically allocated memory units before the downgrade to a physical segment with fixed allocated memory units after the downgrade. Obtain the virtual segment within the local transaction log module, mark the virtual segment, and obtain the virtual segment to be released; Perform a resource release operation on the virtual segment to be released; Based on a preset release cycle, the release status of the virtual segment to be released is periodically detected; If all the release statuses are detected as complete, then the management structure quantity update operation is performed on the local transaction log module.

3. The method according to claim 2, characterized in that, The step of performing a resource release operation on the virtual segment to be released includes: Obtain the access frequency and latest usage time of the virtual segment to be released; Based on the preset weighting factor, the access frequency, and the latest usage time, the virtual segment to be released is weighted and calculated to obtain the weight value of the virtual segment to be released. Based on the weight values, the virtual segments to be released are sorted to obtain the execution order table of the virtual segments to be released; Based on the execution order table, a resource release operation is performed on the virtual segment to be released.

4. The method according to claim 3, characterized in that, After periodically detecting the release status of the virtual segment to be released based on a preset release cycle, the method further includes: If a virtual segment to be released is detected as not having been fully released, and the current detection duration exceeds a preset timeout threshold, then a rewrite operation is performed on the data in the virtual segment to be released; the rewrite operation refers to rewriting data conforming to the virtual segment format into data conforming to the physical segment format. The data conforming to the physical segment format is stored in the physical segment, and the data conforming to the virtual segment format is deleted; Update the release status of the virtual segment to be released to "release complete" and synchronize the release status to the controller on the other side.

5. The method according to claim 4, characterized in that, The step of performing a management structure quantity update operation on the local transaction log module includes: Obtain the memory usage status data of the dual-controller storage system; Based on the memory usage status data, calculate the minimum number of management structures required for the downgraded transaction log module; Based on the minimum number of management structures, perform a management structure number update operation on the local transaction log module.

6. The method according to any one of claims 1-5, characterized in that, After performing the process recovery operation on the contralateral controller, the method further includes: Based on a preset load distribution strategy, business migration scheduling is performed until the dual-controller storage system reaches a load-balanced state.

7. An online degradation device for a transaction log module, characterized in that, include: The detection module is used to detect whether the transaction log module includes a degradation flag based on a preset detection period. The first migration module is used, if included, to simulate process failure of the local controller and migrate the business logic services carried by the local controller to the counterpart controller. The first update module is used to perform a version update operation on the local controller; The first recovery module is used to perform a process recovery operation on the local controller if the local controller completes a version update. The second migration module is used to simulate process failure of the counterpart controller after the local controller process is restored, and to migrate the business logic services carried by the counterpart controller to the local controller. The second update module is used to perform a version update operation on the contra-side controller; The second recovery module is used to perform a process recovery operation on the counterpart controller if the counterpart controller completes a version update.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images