Abnormality processing method and device, electronic equipment and computer program product

Abstract

The application relates to the technical field of business processing, and provides an exception processing method and device, electronic equipment and a computer program product, the method comprising the following steps: receiving fuse information sent by a front-end system, and responding to interface business requests triggered by each business process; determining an exception business request in each interface business request according to the fuse information, blocking the exception business request, and sending the exception business request to the front-end system; receiving recovery information sent by the front-end system based on the exception business request, and performing recovery processing on the exception business request according to the recovery information. The exception processing method provided in the application embodiment accurately determines the exception business request in each interface business request according to the fuse information, blocks the exception business request, and does not pass all the exception business requests and normal business requests, so that the blocking of the normal business requests is reduced, and the business continuity of the normal business is improved.

Description

Technical Field

[0001] This application relates to the field of business processing technology, and in particular to an exception handling method, apparatus, electronic device, and computer program product. Background Technology

[0002] In the existing NGBOSS system, the core devices CBE and BILL have been gradually clustered and containerized. However, BDS, constrained by its database and dual-machine architecture, has become a risk point for the entire system. Users involved in services such as mobile home networking, group payment, and Aurora Broadband are distributed across different BDS devices. Therefore, service access between devices CBE and BILL, and between CBE and BILL, is no longer a simple tree-like access but a mesh-like access.

[0003] In the existing NGBOSS system, when one or more BDS devices fail, the system cannot accurately pinpoint the abnormal service carried by the user on the failed BDS. Therefore, the usual approach is to allow all services (abnormal and normal services), which results in the blockage of normal services and reduces the service continuity of normal services. Summary of the Invention

[0004] This application provides an exception handling method, apparatus, electronic device, and computer program product, which aim to improve business continuity in normal operations.

[0005] Firstly, this application provides an exception handling method, including:

[0006] Receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes;

[0007] Based on the circuit breaker information, abnormal service requests in each of the interface service requests are identified, the abnormal service requests are blocked, and the abnormal service requests are sent to the front-end system.

[0008] Receive recovery information sent by the front-end system based on the abnormal service request, and perform recovery processing on the abnormal service request according to the recovery information.

[0009] In one embodiment, the step of determining the abnormal service requests among the various interface service requests based on the circuit breaker information includes:

[0010] The circuit breaker system is determined by the circuit breaker information, and the system to be accessed by each of the interface service requests is determined.

[0011] Determine whether there exists a target system that matches the circuit breaker system in each of the systems to be accessed;

[0012] If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed will be identified as the abnormal service request.

[0013] Secondly, this application provides an exception handling method, including:

[0014] The circuit breaker information is determined based on the faulty circuit breaker system, and the circuit breaker information is synchronized to the cluster service system;

[0015] Receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests;

[0016] The recovery information after the circuit breaker system is repaired is sent to the cluster service system.

[0017] In one embodiment, the step of determining the fuse information based on the faulty fuse system includes:

[0018] The status of the service interfaces of each system is detected at a first preset time interval, wherein the status of the service interfaces includes a disconnected state;

[0019] Determine whether the circuit breaker system exists in each system, wherein the number of consecutive times the service interface of the circuit breaker system is in a disconnected state exceeds a preset threshold.

[0020] If the circuit breaker system exists, the circuit breaker information is determined based on the status of the circuit breaker system and its corresponding service interface.

[0021] The step of determining the fuse information based on the faulty fuse system includes:

[0022] Obtain business processing data from each system within a second preset time period, wherein the business processing data includes successful business processing data and failed business processing data;

[0023] The success rate of business processing for each system is determined based on the success and failure data of business processing for each system.

[0024] Determine whether the circuit breaker system exists in each system, wherein the business processing success rate of the circuit breaker system is less than a preset success rate threshold;

[0025] If the circuit breaker system exists, the circuit breaker information is determined based on the circuit breaker system and its corresponding business processing success rate.

[0026] The step of determining the fuse information based on the faulty fuse system includes:

[0027] Determine the continuous delay duration of each system during the business processing;

[0028] Determine whether the circuit breaker system exists in each system, wherein the continuous delay duration of the circuit breaker system is greater than a preset delay threshold;

[0029] If the aforementioned circuit breaker system exists, the circuit breaker information is determined based on the circuit breaker system and its corresponding continuous delay duration.

[0030] Thirdly, this application also provides an anomaly handling apparatus, comprising:

[0031] The response receiving module is used to receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes.

[0032] The first sending module is used to determine the abnormal service requests in each of the interface service requests based on the circuit breaker information, to block the abnormal service requests, and to send the abnormal service requests to the front-end system.

[0033] The processing module is used to receive recovery information sent by the front-end system based on the abnormal service request, and to perform recovery processing on the abnormal service request according to the recovery information.

[0034] Fourthly, this application also provides an anomaly handling apparatus, comprising:

[0035] The synchronization module is used to determine the circuit breaker information based on the faulty circuit breaker system and synchronize the circuit breaker information to the cluster service system;

[0036] The repair module is used to receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests;

[0037] The second sending module is used to send the recovery information after the circuit breaker system is repaired to the cluster service system.

[0038] Fifthly, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the exception handling method described in the first aspect.

[0039] In a sixth aspect, this application also provides a computer program product, the computer program product comprising a computer program, which, when executed by the processor, implements the steps of the exception handling method described in the first aspect.

[0040] The exception handling method, apparatus, electronic device, and computer program product provided in this application accurately determine the abnormal business requests in each interface business request based on the circuit breaker information during the exception handling process, and block the abnormal business requests, rather than allowing both abnormal and normal business requests when it is determined that there are abnormal business requests. This reduces the blocking of normal business requests and improves the business continuity of normal services. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is one of the flowcharts illustrating the exception handling method provided in this application;

[0043] Figure 2 This is the second flowchart of the exception handling method provided in this application;

[0044] Figure 3 This is one of the structural schematic diagrams of the anomaly handling device provided in this application;

[0045] Figure 4 This is the second schematic diagram of the anomaly handling device provided in this application;

[0046] Figure 5 This is a schematic diagram of the structure of the electronic device provided in this application. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0048] The following is combined with Figures 1 to 5 This application describes the exception handling method, apparatus, electronic device, and computer program product provided.

[0049] Specifically, this application provides an exception handling method, referring to... Figures 1 to 5 , Figure 1 This is one of the flowcharts illustrating the exception handling method provided in this application; Figure 2This is the second flowchart of the exception handling method provided in this application; Figure 3 This is one of the structural schematic diagrams of the anomaly handling device provided in this application; Figure 4 This is the second schematic diagram of the anomaly handling device provided in this application; Figure 5 This is a schematic diagram of the structure of the electronic device provided in this application.

[0050] This application provides an embodiment of an exception handling method. It should be noted that although the logical order is shown in the flowchart, under certain data conditions, the steps shown or described may be performed in a different order than that shown here.

[0051] Specifically, refer to Figure 1 , Figure 1 This is one of the flowcharts illustrating the exception handling method provided in this application. The exception handling method provided in this application includes:

[0052] Step S10: Receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes.

[0053] It should be noted that the execution subject of the exception handling method provided in this application embodiment can be a cluster service system, wherein the cluster service system includes, but is not limited to, the CBE cluster service system, the BILL cluster service system, and the BDS cluster service system.

[0054] Furthermore, before sending circuit breaker information to the cluster service system, the front-end system needs to create circuit breaker monitoring. The number of circuit breaker monitoring devices depends on the complexity of the cluster service system; the higher the complexity, the more monitoring devices are needed, and vice versa. The minimum number of monitoring devices is generally two. Next, the front-end system monitors the business status of the cluster service system through circuit breaker monitoring, including but not limited to business interface status, business processing success rate, and business processing delay duration, and determines whether there are any anomalies in these parameters. If abnormal business operations are found, the corresponding abnormal cluster service system (i.e., the circuit breaker system) is identified, and corresponding circuit breaker information is generated based on the circuit breaker system. Finally, the front-end system synchronizes the generated circuit breaker information to the cluster service system.

[0055] It should be further noted that, since the impact on business is negligible when the CBE cluster service system and BILL cluster service system are abnormal, the BDS cluster service system may block business and seriously affect the stability of the system when it is abnormal. Therefore, the abnormal cluster service system (circuit breaker system) in this application embodiment usually refers to the BDS cluster service system. Thus, abnormality includes, but is not limited to, BDS system memory database failure, BDS system host failure, and BDS system business abnormality.

[0056] Furthermore, when the cluster service system receives the circuit breaker information sent by the front-end system, it stores the circuit breaker information in the system node memory segment (program cache). When a business process is detected to have triggered the circuit breaker, the cluster service system responds to the interface business requests triggered by each business process and reads the circuit breaker information from the system node memory segment.

[0057] It should be noted that, in order to avoid affecting the processing efficiency of business processes, this embodiment writes the circuit breaker information into the system node memory segment instead of storing the circuit breaker information in the system database or as a system file, due to the large number of concurrent applications or devices.

[0058] Step S20: Based on the circuit breaker information, determine the abnormal service requests in each of the interface service requests, block the abnormal service requests, and send the abnormal service requests to the front-end system.

[0059] The cluster service system determines the systems that each business process's interface service request is intended to access. Based on the circuit breaker information, it determines whether any abnormal systems exist within those systems. If an abnormal system is identified, the cluster service system classifies the interface service request corresponding to that abnormal system as an abnormal service request, as described in steps S201 to S203. Next, the cluster service system blocks the abnormal service request, either by storing it in an exception queue or by handling the exception request as a failure. Finally, the cluster service system generates an exception return code based on the abnormal service request and sends this code to the front-end system.

[0060] Furthermore, the CBE cluster service system processes call detail records (CDRs) and communication messages, stores abnormal service requests in an exception queue, and sends exception return codes to the front-end system. The BILL cluster service system processes CRM (Customer Relationship Management) requests, handles failures of abnormal service requests, and sends exception return codes to the front-end system. The BDS cluster service system processes payment information across regions or across BDS nodes, handles failures of abnormal service requests, and sends exception return codes to the front-end system.

[0061] Furthermore, the specific descriptions of steps S201 to S203 are as follows:

[0062] Step S201: Determine the circuit breaker system of the circuit breaker information, and determine the respective systems to be accessed by each of the interface service requests;

[0063] Step S202: Determine whether there is a target system to be accessed that is consistent with the circuit breaker system in each of the systems to be accessed;

[0064] Step S203: If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed is determined as the abnormal service request.

[0065] Specifically, the cluster service system determines the circuit breaker system corresponding to the circuit breaker information and the various systems to be accessed by each interface service request based on the circuit breaker information. Next, the cluster service system determines whether a target system consistent with the circuit breaker system exists among the various systems to be accessed. If a target system exists among the various systems to be accessed, the cluster service system classifies the interface service request corresponding to the target system as an abnormal service request. If a target system does not exist among the various systems to be accessed, the cluster service system determines that there are no abnormal service requests among the interface service requests.

[0066] In this embodiment, for example, there are two interface service requests: Interface service request 1 "The system to be accessed is BDS-1" and Interface service request 2 "The system to be accessed is BDS-2". The circuit breaker information is "The service interface status of BDS-1 in the BDS cluster service system is abnormal". Therefore, the circuit breaker system is determined to be "BDS-1" and Interface service request 1 is determined to be an abnormal service request.

[0067] The embodiments of this application determine abnormal service requests based on the consistency between the circuit breaker system and each system to be accessed, thereby ensuring the accuracy of the determined abnormal service requests.

[0068] Step S30: Receive recovery information sent by the front-end system based on the abnormal service request, and perform recovery processing on the abnormal service request according to the recovery information.

[0069] After the cluster service system sends the exception return code of the abnormal business request to the front-end system, the front-end system determines the circuit breaker system with the exception based on the exception return code and repairs the circuit breaker system. It should be noted that the repair in this embodiment can be automatic repair by the front-end system or manual repair. Due to the complexity of the system, in order to accurately repair the circuit breaker system, this embodiment prioritizes manual repair. Further, it can be understood that the front-end system sends the circuit breaker system repair information to the user terminal. After receiving the repair information through the user terminal, the user repairs the circuit breaker system according to the repair information. After the repair is completed, the user terminal sends recovery information to the front-end system. After receiving the recovery information sent by the user terminal, the front-end system sends the recovery information to the cluster service system.

[0070] Furthermore, when the cluster service system receives recovery information from the front-end system, it performs recovery processing on the abnormal service requests based on the recovery information. In this embodiment, for example, for the CBE cluster service system, upon receiving recovery information from the front-end system, it reclaims the call detail records (CDRs) in the abnormal queue and performs batch pricing processing.

[0071] This embodiment provides an exception handling method. During the exception handling process, abnormal business requests in each interface business request are accurately identified based on the circuit breaker information, and these abnormal business requests are blocked, rather than allowing both abnormal and normal business requests when an abnormal business request is identified. This reduces the blocking of normal business requests and improves the business continuity of normal services. Furthermore, by blocking abnormal business requests, this embodiment prevents system blockage and improves system stability.

[0072] Furthermore, referring to Figure 2 , Figure 2 This is a second flowchart illustrating the exception handling method provided in this application. The exception handling method provided in this application includes:

[0073] Step S40: Determine the circuit breaker information based on the faulty circuit breaker system, and synchronize the circuit breaker information to the cluster service system;

[0074] Step S50: Receive the abnormal service request returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service request;

[0075] Step S60: Send the recovery information of the circuit breaker system after repair to the cluster service system.

[0076] It should be noted that the execution subject of the exception handling method provided in this application embodiment can be a front-end system. The front-end system connects and communicates with the cluster service system. At the same time, the front-end system monitors the cluster service system through circuit breaker monitoring.

[0077] The front-end system monitors the business interface status of each BDS system in the BDS cluster service system via circuit breaking, and determines whether there are any abnormal BDS systems (circuit-breaking systems) based on the business interface status. Simultaneously, the front-end system monitors the business processing success rate of each BDS system in the BDS cluster service system via circuit breaking, and determines whether there are any abnormal BDS systems based on the business processing success rate. Furthermore, the front-end system monitors the business processing delay duration of each BDS system in the BDS cluster service system via circuit breaking, and determines whether there are any abnormal BDS systems based on the business processing delay duration. If a faulty BDS system is identified based on the business interface status, and / or the business processing success rate, and / or the business processing delay duration, the front-end system identifies the faulty circuit-breaking system and determines the circuit-breaking information based on the faulty circuit-breaking system, as detailed in steps S401 to S410.

[0078] Next, the front-end system sends the circuit breaker information to the cluster service systems (CBE cluster service system, BILL cluster service system, and BDS cluster service system). It should be noted that during the process of synchronizing the circuit breaker information to the CBE cluster service system, BILL cluster service system, and BDS cluster service system, the front-end system needs to determine whether the circuit breaker information synchronized to the CBE cluster service system, BILL cluster service system, and BDS cluster service system is consistent. If it is determined that they are inconsistent, the front-end system will reclaim the circuit breaker information and then resend the circuit breaker information to the CBE cluster service system, BILL cluster service system, and BDS cluster service system. This process is repeated until the circuit breaker information in the CBE cluster service system, BILL cluster service system, and BDS cluster service system is consistent.

[0079] Furthermore, when the cluster service system receives circuit breaker information from the front-end system, it stores the circuit breaker information in the system node's memory segment. Upon detecting a business process triggering a circuit breaker, the cluster service system responds to the interface business requests triggered by each business process and reads the circuit breaker information from the system node's memory segment. Simultaneously, the cluster service system determines the systems that the interface business requests triggered by each business process intend to access. Based on the circuit breaker information, it determines whether any abnormalities exist in the systems to be accessed. If an abnormal system is identified, the cluster service system classifies the interface business request corresponding to the abnormal system as an abnormal business request. Next, the cluster service system blocks the abnormal business request, either by storing it in an exception queue or by handling the abnormal business request as a failure. Finally, the cluster service system generates an exception return code based on the abnormal business request and sends the exception return code to the front-end system.

[0080] When the front-end system receives an exception return code from the cluster service system for an abnormal business request, it identifies the faulty circuit breaker system based on the exception return code and sends the repair information for the circuit breaker system to the user terminal. The user receives the repair information through their terminal and repairs the circuit breaker system accordingly. After the repair is complete, the user terminal sends recovery information to the front-end system. Upon receiving the recovery information from the user terminal, the front-end system forwards the recovery information to the cluster service system.

[0081] This embodiment provides an exception handling method that automatically and intelligently determines circuit breaker and recovery information and sends them to the cluster service system, thereby enabling comprehensive and intelligent management of the system, preventing system congestion, and maintaining system stability.

[0082] Furthermore, the specific descriptions of steps S401 to S403 are as follows:

[0083] Step S401: Detect the service interface status of each system at a first preset time interval, wherein the service interface status includes a disconnected state.

[0084] Step S402: Determine whether the circuit breaker system exists in each system, wherein the number of consecutive times the service interface of the circuit breaker system is in a disconnected state is greater than a preset threshold number.

[0085] Step S403: If the circuit breaker system exists, determine the circuit breaker information based on the status of the circuit breaker system and its corresponding service interface.

[0086] Specifically, the front-end system probes the business interface status of each BDS system in the BDS cluster service system at first preset intervals, determining the probe status of each BDS system's business interface for each probe. The probe status includes connectivity and disconnection. The first preset interval is set based on actual conditions. Next, the front-end system judges each BDS system according to an anomaly rule based on the number of consecutive disconnection instances. Specifically, it determines whether there is an abnormal BDS system whose consecutive disconnection instances exceed a preset threshold, which is set based on actual conditions. If an abnormal BDS system is determined, the front-end system identifies it as a circuit breaker system. Finally, the front-end system determines the anomaly information based on the business interface status and packages the circuit breaker system and the anomaly information to obtain the circuit breaker information for the circuit breaker system.

[0087] In this embodiment, the preset number of times threshold is 3 times, the first preset duration is 100 milliseconds, if the front-end system detects that the service interface status of the BDS-1 system is not connected within 300 milliseconds, then the BDS-1 system is identified as a circuit breaker system, the abnormal information is "service interface blockage", and the final circuit breaker information is "service interface blockage of the BDS-1 system".

[0088] This application embodiment automatically monitors the circuit breaker system through the status of the business interface, thereby enabling intelligent fault monitoring and further intelligent determination of circuit breaker information.

[0089] Furthermore, the specific descriptions of steps S404 to S407 are as follows:

[0090] Step S404: Obtain business processing data of each system within a second preset time period, wherein the business processing data includes business processing success data and business processing failure data;

[0091] Step S405: Determine the business processing success rate of each system based on the business processing success data and business processing failure data of each system;

[0092] Step S406: Determine whether the circuit breaker system exists in each system, wherein the business processing success rate of the circuit breaker system is less than a preset success rate threshold;

[0093] Step S407: If the circuit breaker system exists, determine the circuit breaker information based on the circuit breaker system and its corresponding business processing success rate.

[0094] Specifically, the front-end system acquires business processing data from each BDS system within a second preset time period, identifying successful and failed business processing data for each BDS system. The second preset time period is set based on actual circumstances. Next, the front-end system calculates the business processing success rate for each BDS system based on the successful and failed data: Business processing success rate = (Successful data / (Successful data + Failed data)) * 100%. Then, the front-end system compares the business processing success rate of each BDS system with a preset success rate threshold to determine if any BDS systems have an abnormal success rate below the threshold. The preset success rate threshold is also set based on actual circumstances.

[0095] If an abnormal BDS system with a business processing success rate lower than a preset success rate threshold is identified among the various BDS systems, the front-end system designates this abnormal BDS system as a circuit breaker system. Simultaneously, it determines the corresponding exception information based on the business processing success rate. Since the business processing success rate is related to the level of business activity, it can be further refined as follows: If the business processing success rate is determined to be less than a first threshold, the front-end system determines the business is in a highly busy state, and the exception information is "highly busy." If the business processing success rate is determined to be less than a second threshold but greater than or equal to the first threshold, the front-end system determines the business is in a moderately busy state, and the exception information is "moderately busy." If the business processing success rate is determined to be less than a third threshold but greater than or equal to the second threshold, the front-end system determines the business is in a slightly busy state, and the exception information is "slightly busy." The first, second, and third thresholds are all set based on actual conditions. Finally, the front-end system packages the circuit breaker system and the exception information to obtain the circuit breaker information.

[0096] This application embodiment uses an automatic monitoring and circuit breaker system for business processing success rate to intelligently monitor faults and further intelligently determine circuit breaker information.

[0097] Furthermore, the specific descriptions of steps S408 to S410 are as follows:

[0098] Step S408: Determine the continuous delay duration of each system during the business processing;

[0099] Step S409: Determine whether the circuit breaker system exists in each system, wherein the continuous delay duration of the circuit breaker system is greater than a preset delay threshold.

[0100] Step S410: If the fuse system exists, determine the fuse information based on the fuse system and its corresponding continuous delay duration.

[0101] Specifically, the front-end system determines the continuous delay duration of each BDS system during the business processing, and compares the continuous delay duration with a preset delay threshold to determine whether there are any abnormal BDS systems whose continuous delay duration exceeds the preset delay threshold. The preset delay threshold is set according to the actual situation.

[0102] If an abnormal BDS system with a continuous delay duration exceeding a preset delay threshold is identified among the various BDS systems, the front-end system identifies the abnormal BDS system as a circuit breaker system. Simultaneously, it determines the corresponding anomaly information based on the continuous delay duration. Since the continuous delay duration is related to the business processing speed, it can be further refined as follows: If the continuous delay duration is greater than a first threshold and less than or equal to a second threshold, the front-end system determines that the business processing speed is slow, and the anomaly information is "business processing speed is slow." If the continuous delay duration is greater than the second threshold and less than or equal to a third threshold, the front-end system determines that the business processing speed is moderately slow, and the anomaly information is "business processing speed is moderately slow." If the continuous delay duration is greater than the third threshold, the front-end system determines that the business processing speed is severely slow, and the anomaly information is "business processing speed is severely slow." The first, second, and third thresholds are set based on actual conditions. Finally, the front-end system packages the circuit breaker system and the anomaly information to obtain the circuit breaker information for the circuit breaker system.

[0103] This application embodiment uses a continuous delay duration automatic monitoring fuse system to intelligently monitor faults and further intelligently determine fuse information.

[0104] Furthermore, the exception handling apparatus provided in this application will be described below. The exception handling apparatus described below can be referred to in correspondence with the exception handling method described above.

[0105] like Figure 3 As shown, Figure 3 This is one of the structural schematic diagrams of the exception handling device provided in this application. The exception handling device includes:

[0106] The receiving response module 301 is used to receive the circuit breaker information sent by the front-end system and respond to the interface business requests triggered by each business process.

[0107] The first sending module 302 is used to determine the abnormal service request in each of the interface service requests according to the circuit breaker information, to block the abnormal service request, and to send the abnormal service request to the front-end system;

[0108] The processing module 303 is used to receive recovery information sent by the front-end system based on the abnormal service request, and to perform recovery processing on the abnormal service request according to the recovery information.

[0109] Furthermore, the first sending module 302 includes a first determining unit, configured to:

[0110] The circuit breaker system is determined by the circuit breaker information, and the system to be accessed by each of the interface service requests is determined.

[0111] Determine whether there exists a target system that matches the circuit breaker system in each of the systems to be accessed;

[0112] If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed will be identified as the abnormal service request.

[0113] The specific embodiments of the anomaly handling device provided in this application are basically the same as the embodiments of the above-described anomaly handling methods, and will not be described in detail here.

[0114] like Figure 4 As shown, Figure 4 This is the second structural schematic diagram of the exception handling device provided in this application. The exception handling device includes:

[0115] Synchronization module 401 is used to determine the circuit breaker information based on the circuit breaker system that has failed, and to synchronize the circuit breaker information to the cluster service system;

[0116] Repair module 402 is used to receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests;

[0117] The second sending module 403 is used to send the recovery information after the circuit breaker system is repaired to the cluster service system.

[0118] Furthermore, the synchronization module 401 includes a second determining unit, used for:

[0119] The status of the service interfaces of each system is detected at a first preset time interval, wherein the status of the service interfaces includes a disconnected state;

[0120] Determine whether the circuit breaker system exists in each system, wherein the number of consecutive times the service interface of the circuit breaker system is in a disconnected state exceeds a preset threshold.

[0121] If the circuit breaker system exists, the circuit breaker information is determined based on the status of the circuit breaker system and its corresponding service interface.

[0122] Furthermore, the second determining unit is also used for:

[0123] Obtain business processing data from each system within a second preset time period, wherein the business processing data includes successful business processing data and failed business processing data;

[0124] The success rate of business processing for each system is determined based on the success and failure data of business processing for each system.

[0125] Determine whether the circuit breaker system exists in each system, wherein the business processing success rate of the circuit breaker system is less than a preset success rate threshold;

[0126] If the circuit breaker system exists, the circuit breaker information is determined based on the circuit breaker system and its corresponding business processing success rate.

[0127] Furthermore, the second determining unit is also used for:

[0128] Determine the continuous delay duration of each system during the business processing;

[0129] Determine whether the circuit breaker system exists in each system, wherein the continuous delay duration of the circuit breaker system is greater than a preset delay threshold;

[0130] If the circuit breaker system exists, the circuit breaker information is determined based on the circuit breaker system and its corresponding continuous delay duration.

[0131] The specific embodiments of the anomaly handling device provided in this application are basically the same as the embodiments of the above-described anomaly handling methods, and will not be described in detail here.

[0132] Figure 5 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 5 As shown, the electronic device may include: a processor 510, a communication interface 520, a memory 530, and a communication bus 540, wherein the processor 510, the communication interface 520, and the memory 530 communicate with each other through the communication bus 540.

[0133] Furthermore, the processor 510 can invoke logical instructions in the memory 530 to execute an exception handling method, which includes:

[0134] Receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes;

[0135] Based on the circuit breaker information, abnormal service requests in each of the interface service requests are identified, the abnormal service requests are blocked, and the abnormal service requests are sent to the front-end system.

[0136] Receive recovery information sent by the front-end system based on the abnormal service request, and perform recovery processing on the abnormal service request according to the recovery information.

[0137] Furthermore, the processor 510 can invoke logical instructions in the memory 530 to execute an exception handling method, which includes:

[0138] The circuit breaker information is determined based on the faulty circuit breaker system, and the circuit breaker information is synchronized to the cluster service system;

[0139] Receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests;

[0140] The recovery information after the circuit breaker system is repaired is sent to the cluster service system.

[0141] Furthermore, the logical instructions in the aforementioned memory 530 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium 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 described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0142] On the other hand, this application also provides a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, and when the program instructions are executed by a computer, the computer is able to execute the exception handling method provided by the above methods, the method including:

[0143] Receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes;

[0144] Based on the circuit breaker information, abnormal service requests in each of the interface service requests are identified, the abnormal service requests are blocked, and the abnormal service requests are sent to the front-end system.

[0145] Receive recovery information sent by the front-end system based on the abnormal service request, and perform recovery processing on the abnormal service request according to the recovery information.

[0146] On the other hand, this application also provides a computer program product, the computer program product including a computer program stored on a non-transitory computer-readable storage medium, the computer program including program instructions, and when the program instructions are executed by a computer, the computer is able to execute the exception handling method provided by the above methods, the method including:

[0147] The circuit breaker information is determined based on the faulty circuit breaker system, and the circuit breaker information is synchronized to the cluster service system;

[0148] Receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests;

[0149] The recovery information after the circuit breaker system is repaired is sent to the cluster service system.

[0150] In another aspect, this application also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the exception handling methods provided above, the method comprising:

[0151] Receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes;

[0152] Based on the circuit breaker information, abnormal service requests in each of the interface service requests are identified, the abnormal service requests are blocked, and the abnormal service requests are sent to the front-end system.

[0153] Receive recovery information sent by the front-end system based on the abnormal service request, and perform recovery processing on the abnormal service request according to the recovery information.

[0154] In another aspect, this application also provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to perform the exception handling methods provided above, the method comprising:

[0155] The circuit breaker information is determined based on the faulty circuit breaker system, and the circuit breaker information is synchronized to the cluster service system;

[0156] Receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests;

[0157] The recovery information after the circuit breaker system is repaired is sent to the cluster service system.

[0158] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0159] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments.

[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. An exception handling method, characterized in that, include: Receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes; Based on the circuit breaker information, abnormal service requests in each of the interface service requests are identified, the abnormal service requests are blocked, and the abnormal service requests are sent to the front-end system. Receive recovery information sent by the front-end system based on the abnormal service request, and perform recovery processing on the abnormal service request according to the recovery information; The step of determining the abnormal service requests in each of the interface service requests based on the circuit breaker information includes: The circuit breaker system is determined by the circuit breaker information, and the system to be accessed by each of the interface service requests is determined. Determine whether there exists a target system that matches the circuit breaker system in each of the systems to be accessed; If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed will be identified as the abnormal service request.

2. An exception handling method, characterized in that, include: The circuit breaker information is determined based on the faulty circuit breaker system, and the circuit breaker information is synchronized to the cluster service system; Receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests; The recovery information after the circuit breaker system is repaired is sent to the cluster service system; The abnormal service request is determined in the following way: The circuit breaker system is determined by the circuit breaker information, and the systems to be accessed by each interface service request are determined. Determine whether there exists a target system that matches the circuit breaker system in each of the systems to be accessed; If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed will be identified as the abnormal service request.

3. The anomaly handling method according to claim 2, characterized in that, The step of determining the fuse information based on the faulty fuse system includes: The status of the service interfaces of each system is detected at first preset intervals, wherein the status of the service interfaces includes a disconnected state; Determine whether the circuit breaker system exists in each system, wherein the number of consecutive times the service interface of the circuit breaker system is in a disconnected state exceeds a preset threshold. If the circuit breaker system exists, the circuit breaker information is determined based on the status of the circuit breaker system and its corresponding service interface.

4. The anomaly handling method according to claim 2, characterized in that, The step of determining the fuse information based on the faulty fuse system includes: Obtain business processing data from each system within a second preset time period, wherein the business processing data includes successful business processing data and failed business processing data; The success rate of business processing for each system is determined based on the success and failure data of business processing for each system. Determine whether the circuit breaker system exists in each system, wherein the business processing success rate of the circuit breaker system is less than a preset success rate threshold; If the circuit breaker system exists, the circuit breaker information is determined based on the circuit breaker system and its corresponding business processing success rate.

5. The anomaly handling method according to claim 2, characterized in that, The step of determining the fuse information based on the faulty fuse system includes: Determine the continuous delay duration of each system during the business processing; Determine whether the circuit breaker system exists in each system, wherein the continuous delay duration of the circuit breaker system is greater than a preset delay threshold; If the circuit breaker system exists, the circuit breaker information is determined based on the circuit breaker system and its corresponding continuous delay duration.

6. An anomaly handling device, characterized in that, include: The response receiving module is used to receive circuit breaker information sent by the front-end system and respond to interface business requests triggered by various business processes. The first sending module is used to determine the abnormal service requests in each of the interface service requests based on the circuit breaker information, to block the abnormal service requests, and to send the abnormal service requests to the front-end system. The processing module is used to receive recovery information sent by the front-end system based on the abnormal service request, and to perform recovery processing on the abnormal service request according to the recovery information; The step of determining the abnormal service requests in each of the interface service requests based on the circuit breaker information includes: The circuit breaker system is determined by the circuit breaker information, and the system to be accessed by each of the interface service requests is determined. Determine whether there exists a target system that matches the circuit breaker system in each of the systems to be accessed; If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed will be identified as the abnormal service request.

7. An anomaly handling device, characterized in that, include: The synchronization module is used to determine the circuit breaker information based on the faulty circuit breaker system and synchronize the circuit breaker information to the cluster service system; The repair module is used to receive abnormal service requests returned by the cluster service system based on the circuit breaker information, and repair the circuit breaker system based on the abnormal service requests; The second sending module is used to send the recovery information after the circuit breaker system is repaired to the cluster service system; The abnormal service request is determined in the following way: The circuit breaker system is determined by the circuit breaker information, and the systems to be accessed by each interface service request are determined. Determine whether there exists a target system that matches the circuit breaker system in each of the systems to be accessed; If the target system to be accessed exists, the interface service request corresponding to the target system to be accessed will be identified as the abnormal service request.

8. An electronic device, the electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the exception handling method according to any one of claims 1 to 5.

9. A computer program product, the computer program product comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the exception handling method according to any one of claims 1 to 5.

Images