Service request fusing management method and device, equipment, storage medium and product

Abstract

The embodiment of the invention provides a service request fusing management method and device, equipment, a storage medium and a product. According to the technical scheme provided by the embodiment of the invention, the service request fusing probability value is determined according to the service request number, the request success frequency and the request continuous failure period number of the target service node corresponding to the first service request in the preset statistical period, and the preset fusing sensitive value and the period window number; according to the service request fusing probability value, the first service request is determined to pass or reject according to the service request fusing probability value, the fusing strength can be dynamically adjusted according to the historical response condition of the service node to the service request, the whole service does not need to be fused, the user request failure rate is effectively reduced, and the fusing effect and the service reliability of the service request are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a service request fuse management method, apparatus, device, storage medium, and product. Background Art

[0002] With the rapid development of the Internet and computer technology, the user scale of social platforms continues to expand. Especially when holding large-scale events such as annual ceremonies, social platforms need to carry a large number of concurrent requests, which puts enormous pressure on services. In this scenario, some microservice nodes may fail due to traffic overload, response timeout, etc., resulting in service unavailability. At this time, it is necessary to perform certain fuses on the microservice client, otherwise it is easy to consume too much service resources and downstream services cannot bear it, causing system avalanche and affecting user experience.

[0003] The existing circuit breaker mechanism usually breaks the entire service. When a circuit breaker occurs, the service is completely in a circuit breaker rejection state. The circuit breaker method is too aggressive and often directly rejects all service requests, resulting in an increase in the failure rate of user requests and poor circuit breaker effect of service requests. Summary of the invention

[0004] The embodiments of the present application provide a service request fuse management method, device, equipment, storage medium and product to solve the technical problems in the related technology that the fuse means are too aggressive and the fuse effect of the service request is poor. The fuse strength can be dynamically adjusted to effectively reduce the user request failure rate and improve the fuse effect of the service request.

[0005] In a first aspect, an embodiment of the present application provides a service request fuse management method, including:

[0006] In the case of receiving a first service request, determining the number of service requests for a second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests for the second service request, and the number of consecutive request failure cycles, where the number of consecutive request failure cycles is the number of period windows in which a response to the second service request is to reject the second service request;

[0007] Determine the service request fuse probability value according to the number of service requests, the number of successful requests and the number of consecutive request failure cycles, as well as the preset fuse sensitivity value and the number of cycle windows;

[0008] Determine whether to approve or reject the first service request according to the service request fuse probability value.

[0009] In a second aspect, an embodiment of the present application provides a service request fuse management device, including a request response module, a probability determination module and a request processing module, wherein:

[0010] The request response module is configured to determine, upon receiving the first service request, the number of service requests for the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests for the second service request, and the number of consecutive request failure cycles, wherein the number of consecutive request failure cycles is the number of period windows in which the response mode to the second service request is to reject the second service request;

[0011] The probability determination module is configured to determine the service request fuse probability value according to the number of service requests, the number of successful requests and the number of consecutive request failure cycles, as well as a preset fuse sensitivity value and a number of cycle windows;

[0012] The request processing module is configured to determine whether to approve or reject the first service request according to the service request fuse probability value.

[0013] In a third aspect, an embodiment of the present application provides a service request fuse management device, including: a memory and one or more processors;

[0014] The memory is used to store one or more programs;

[0015] When the one or more programs are executed by the one or more processors, the one or more processors implement the service request fuse management method as described in the first aspect.

[0016] In a fourth aspect, an embodiment of the present application provides a non-volatile storage medium storing computer executable instructions, wherein the computer executable instructions, when executed by a computer processor, are used to execute the service request fuse management method as described in the first aspect.

[0017] In the fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program, which is stored in a computer-readable storage medium, and at least one processor of the device reads and executes the computer program from the computer-readable storage medium, so that the device performs the service request fuse management method as described in the first aspect.

[0018] The embodiment of the present application determines a service request fuse probability value based on the number of service requests, the number of successful requests, and the number of consecutive request failure cycles of the target service node corresponding to the first service request within a preset statistical period, as well as a preset fuse sensitivity value and the number of period windows, and determines whether to pass or reject the first service request based on the service request fuse probability value. The fuse strength can be dynamically adjusted according to the historical response of the service node to the service request, without the need to fuse the entire service, thereby effectively reducing the user request failure rate and improving the fuse effect and service reliability of the service request. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 It is a flow chart of a service request fuse management method provided by an embodiment of the present application;

[0020] Figure 2 It is a flowchart of another service request fuse management method provided by an embodiment of the present application;

[0021] Figure 3 This is a schematic diagram of a flow chart for determining a service request fuse probability value provided by an embodiment of the present application;

[0022] Figure 4 It is a structural diagram of a service request fuse management device provided in an embodiment of the present application;

[0023] Figure 5 It is a structural diagram of a service request fuse management device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical scheme and advantages of the present application clearer, the specific embodiments of the present application are further described in detail below in conjunction with the accompanying drawings. It is understood that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for the convenience of description, only the part related to the present application but not all of the content is shown in the accompanying drawings. Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow chart describes each operation (or step) as a sequential process, many of the operations therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of each operation can be rearranged. The above process can be terminated when its operation is completed, but it can also have additional steps not included in the accompanying drawings. The above process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.

[0025] The service request circuit breaker management method provided in this application can be applied to service request circuit breaker management under a microservice call system. It aims to dynamically adjust the circuit breaker strength according to the historical response of the service node to the service request. It does not need to fuse the entire service, effectively reducing the user request failure rate and improving the circuit breaker effect of the service request.

[0026] In the existing service request fuse mechanism, the entire service is usually fused, rather than for a specific access node. When a fuse occurs, all service requests are often directly rejected, resulting in an increased failure rate of user requests. For example, when the circuit breaker mode of the fuse tool library Hystrix is ​​in the open state, the service will be completely in a fuse rejection state. In some scenarios with a large number of requests, there will be many request failures, and its fuse means are too radical. The fuse scheme based on a fixed fuse threshold (K value) cannot be flexibly adjusted when dealing with dynamic loads, resulting in a large number of requests being discarded if the fuse threshold is set too small, and it is difficult to effectively trigger the fuse if the fuse threshold is set too large. Based on this, a service request fuse management method according to an embodiment of the present application is provided to solve the technical problem that the existing fuse scheme is too radical and the fuse effect of the service request is poor.

[0027] Figure 1 A flowchart of a service request fuse management method provided in an embodiment of the present application is given. The service request fuse management method provided in an embodiment of the present application can be executed by a service request fuse management device, which can be implemented by hardware and / or software and integrated in the service request fuse management device.

[0028] The following description takes the service request fuse management device executing the service request fuse management method as an example.

[0029] refer to Figure 1 , the service request fuse management method includes:

[0030] S110: upon receiving the first service request, determining the number of service requests of the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests passing the second service request, and the number of consecutive request failure cycles.

[0031] In one embodiment, the service request fuse management device provided by the present solution can be configured in a microservice calling system, and multiple service request fuse management devices and multiple service nodes can be configured in the microservice calling system, wherein multiple service request fuse management devices can be configured in the same or different servers. Similarly, multiple service nodes can also be configured in the same or different servers, wherein the service request fuse management device can be configured with one or more services, and each service can be deployed in one or more service nodes.

[0032] This solution moves the fuse object from the overall service to the specific service node. Each service node contains multiple attributes (such as region, computer room (idcId), host (host), port (port) and node type (nodeType), etc.), where the node type of the service node can be a database (such as Redis, MySQL, Oracle, HBase, etc.), remote procedure call (RPC) service and service call (Feign call), etc. When a service node triggers a fuse (that is, the service request is rejected), the service request can be routed to other available service nodes according to the node sequence of the same machine, computer room and region to ensure maximum service availability.

[0033] The service request provided by this scheme includes a first service request and a second service request. The first service request can be understood as the service request currently received by the service request fuse management device, and the second service request can be understood as the service request received by the service node before (for example, within a preset statistical period). In one embodiment, the service request fuse management device records and maintains the number of service requests corresponding to the second service request received by each service node within the preset statistical period, the number of successful requests corresponding to the second service request (i.e., responding to the second service request), and the number of consecutive request failure cycles, wherein there are multiple cycle windows in a statistical period, and each cycle window records the number of service requests, the number of successful requests, the number of failed requests, and the response method to the second service request (passing or rejecting the second service request) within the corresponding time period. One or more combinations of the above. The number of consecutive request failure cycles is the number of period windows in which the response mode to the second service request is to reject the second service request. For example, the preset statistical period includes windows 1-5, there is a response mode of rejecting the second service request in window 1, there is no response mode of rejecting the second service request in window 2, and there is a response mode of rejecting the second service request in windows 2-5 (the number of period windows in which the response mode to the second service request is to reject the second service request is 3), then the number of consecutive request failure cycles is 3. In one embodiment, the number of consecutive request success cycles is the number of period windows in which the response mode to the second service request is to pass the second service request. For example, the preset statistical period includes windows 1-5, there is a response mode of rejecting the second service request in window 1, there is no response mode of rejecting the second service request in windows 2-4 (the number of period windows in which the response mode to the second service request is to pass the second service request is 3), and there is a response mode of rejecting the second service request in window 5, then the number of consecutive request success cycles is 3.

[0034] Exemplarily, when a first service request sent by a user terminal is received, a target service node that can provide the service required by the first service request is determined from multiple service nodes based on the first service request, and the number of service requests, the number of successful requests, and the number of consecutive request failure cycles of the target service node within a preset statistical period are determined.

[0035] S120: Determine a service request fuse probability value according to the number of service requests, the number of successful requests, the number of consecutive request failure cycles, and a preset fuse sensitivity value and the number of cycle windows.

[0036] Exemplarily, after determining the number of service requests, the number of successful requests, and the number of consecutive request failure cycles of the target service node within a preset statistical period, the service request fuse probability value can be determined based on the number of service requests, the number of successful requests, and the number of consecutive request failure cycles, as well as the preset fuse sensitivity value and the number of period windows.

[0037] The number of periodic windows is the number of periodic windows existing in a preset statistical period. For example, if the preset statistical period period=10s, the length of each periodic window barrel=250ms, then the number of periodic windows totalBarrel=10s / 250ms=40.

[0038] In one embodiment, the service request fuse probability value provided by the present solution is negatively correlated with the number of successful requests and positively correlated with the number of consecutive request failure cycles. Optionally, the fuse sensitivity value, the number of successful requests, and the ratio of the number of cycle windows to the number of consecutive request failure cycles can be multiplied, the number of service requests can be subtracted from the multiplication result, and the ratio of the subtraction result to the number of service requests or the sum of the number of service requests and a preset coefficient (such as 1) can be used as the service request fuse probability value. It can also be the product of the fuse sensitivity value minus the preset coefficient (such as the difference between the fuse sensitivity value and the preset sensitive value or other numerical value), the number of successful requests, and the ratio of the number of consecutive request failure cycles to the number of cycle windows, the number of service requests can be subtracted from the multiplication result, and the ratio of the subtraction result to the number of service requests or the sum of the number of service requests and a preset coefficient (such as 1) can be used as the service request fuse probability value. Optionally, the minimum value of the service request fuse probability value can be set to 0 or other preset thresholds.

[0039] S130: Determine whether to approve or reject the first service request according to the service request fuse probability value.

[0040] After determining the fuse probability threshold, the first service request is passed or rejected according to the service request fuse probability value. Optionally, when rejecting the first service request, the first service request can be routed to other service nodes within a preset number of retries, and the response method to the first service request is determined at the other service nodes based on the service request fuse management method.

[0041] In one embodiment, when determining the response method to the first service request based on the service request fuse probability value, a random number can be randomly generated within a set range (the first sub-range in the set range corresponds to the service request fuse probability value). When the random number is within the first sub-range of the fuse probability threshold, it is considered that the random number hits the service request fuse probability value, and the first service request is rejected. When the random number is outside the first sub-range of the fuse probability threshold, it is considered that the random number does not hit the service request fuse probability value, and the first service request is approved.

[0042] For example, assuming that the value range of the fuse probability threshold is 0 to 1, the fuse probability threshold is a, and a random number is randomly generated between 0 and 100. When the random number is in the range of 0 to b (where b is the result of rounding down a*100), the service request is rejected, and when the random number is in the range of 0 to (b+1), the service request is approved.

[0043] In the above, by determining the service request fuse probability value based on the number of service requests, the number of successful requests and the number of consecutive request failure cycles of the target service node corresponding to the first service request within a preset statistical period, as well as the preset fuse sensitivity value and the number of period windows, and determining whether to pass or reject the first service request based on the service request fuse probability value, the fuse strength can be dynamically adjusted according to the historical response of the service node to the service request, without the need to fuse the entire service, effectively reducing the user request failure rate and improving the fuse effect and service reliability of the service request.

[0044] Based on the above embodiments, Figure 2 A flowchart of another service request fuse management method provided in an embodiment of the present application is given, and the service request fuse management method is a specific embodiment of the above service request fuse management method. Figure 2 , the service request fuse management method includes:

[0045] S210: upon receiving the first service request, determining the number of service requests of the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests passing the second service request, and the number of consecutive request failure cycles.

[0046] S220: Determine a target fuse sensitivity value according to the number of consecutive request failure cycles, the preset fuse sensitivity value, and the number of cycle windows.

[0047] S230: Determine a service request fuse probability value according to the number of service requests, the number of successful requests, and the target fuse sensitivity value.

[0048] Exemplarily, after determining the number of service requests, the number of successful requests, and the number of consecutive request failure cycles, the target fuse sensitivity value may be determined based on the determined number of consecutive request failure cycles and the preset fuse sensitivity value and the number of cycle windows. For example, the fuse sensitivity value may be subtracted from the ratio of the number of consecutive request failure cycles to the number of cycle windows, or the fuse sensitivity value may be subtracted from the product of a preset coefficient (e.g., the difference between the fuse sensitivity value and the preset sensitivity value or other numerical value) and the ratio of the number of consecutive request failure cycles to the number of cycle windows, and the subtraction result may be used as the target fuse sensitivity value. In one embodiment, the fuse sensitivity value may be determined when constructing the fuse.

[0049] In one embodiment, after determining the target fuse sensitivity value, the service request fuse probability value may be determined according to the number of service requests, the number of successful requests, and the target fuse sensitivity value. For example, the product of the number of successful requests and the target fuse sensitivity value is subtracted from the number of service requests, and the ratio of the subtraction result to the number of service requests is used as the service request fuse probability value, or the ratio of the subtraction result to the sum of a preset coefficient (e.g., 1) of the number of service requests is used as the service request fuse probability value.

[0050] This solution determines the target fuse sensitivity value based on the number of consecutive request failure cycles, the preset fuse sensitivity value and the number of cycle windows, and dynamically determines the service request fuse probability value based on the number of service requests, the number of successful requests and the target fuse sensitivity value, dynamically adjusts the fuse strength, and improves the fuse effect and service reliability of service requests.

[0051] In one embodiment, the service request fuse management method provided by the present scheme determines the target fuse sensitivity value based on the number of consecutive request failure cycles, the preset fuse sensitivity value and the number of cycle windows. It can be by multiplying the difference between the preset fuse sensitivity value and the minimum fuse sensitivity threshold with the first ratio of the number of consecutive request failure cycles and the number of cycle windows, subtracting the fuse sensitivity value from the multiplication result, and determining the target fuse sensitivity value based on the subtraction result.

[0052] Exemplarily, after determining the number of service requests, the number of successful requests, and the number of consecutive request failure cycles, the difference between the preset fuse sensitivity value and the minimum fuse sensitivity threshold can be calculated, the difference can be multiplied by the first ratio of the number of consecutive request failure cycles and the number of cycle windows, the fuse sensitivity value can be subtracted from the multiplication result, and the subtraction result can be used as the target fuse sensitivity value. For example, the target fuse sensitivity value can be determined by the following formula:

[0053]

[0054] Among them, K1 is the target fuse sensitivity value, K is the fuse sensitivity value, leastK is the minimum fuse sensitivity threshold, lossBarrel is the number of consecutive request failure cycles, and totalBarrel is the number of cycle windows.

[0055] This solution accurately determines the target fuse sensitivity value based on the preset fuse sensitivity value and the minimum fuse sensitivity threshold, as well as the number of consecutive request failure cycles and the number of cycle windows, dynamically adjusts the fuse strength, and improves the fuse effect and service reliability of service requests.

[0056] In a possible embodiment, the service request fuse management method provided by the present solution subtracts the fuse sensitivity value from the multiplication result, and determines the target fuse sensitivity value according to the subtraction result, which may be to determine the maximum value between the subtraction result and the preset fuse sensitivity minimum threshold, and determine the maximum value as the target fuse sensitivity value. For example, the target fuse sensitivity value may also be determined by the following formula:

[0057]

[0058] This solution determines the magnitude of the current failed requests by calculating the number of consecutive failed cycles / number of cycle windows of consecutive failed requests in multiple cycle windows in the past. If this value is close to 1 (that is, there are many failures), then the calculated target fuse sensitivity value will be relatively small, and it will be easier to discard service requests. If the number of consecutive request failure cycles is relatively small, then the calculated target fuse sensitivity value will be close to the fuse sensitivity value passed by the fuse or backend personnel, and the probability of rejecting the first service request will be greater. This solution accurately determines the target fuse sensitivity value by using the preset fuse sensitivity value and the minimum fuse sensitivity threshold, as well as the number of consecutive request failure cycles and the number of cycle windows, and dynamically adjusts the fuse strength. The minimum fuse sensitivity threshold can ensure the minimum value of the last adjusted fuse sensitivity value, reduce the situation where the fuse strategy is too aggressive, and improve the fuse effect and service reliability of service requests.

[0059] In one possible embodiment, Figure 3 A service request fuse probability value determination process diagram is provided. The service request fuse management method provided in this solution determines the service request fuse probability value according to the number of service requests, the number of successful requests, and the target fuse sensitivity value, including:

[0060] S231: Determine a subtraction result according to the product of the number of service requests and the target fuse sensitivity value and the number of successful requests, and add the number of service requests and the preset number adjustment value to obtain an addition result.

[0061] S232: Determine a second ratio of the subtraction result and the addition result, and determine a service request fuse probability value according to the second ratio.

[0062] Exemplarily, after determining the target fuse sensitivity value, the subtraction result can be determined according to the product of the number of service requests and the target fuse sensitivity value and the number of successful requests. For example, the number of service requests and the product of the target fuse sensitivity value and the number of successful requests are subtracted to obtain the subtraction result. Alternatively, the number of service requests and a preset value (for example, a preset number of traffic protections) and the product of the target fuse sensitivity value and the number of successful requests are subtracted to obtain the subtraction result. The number of service requests and the preset number adjustment value are added to obtain the addition result. For example, if the preset number adjustment value is set to 1, the number of service requests is added by 1 to obtain the addition result.

[0063] In one embodiment, a second ratio of the subtraction result and the addition result determined above is determined, and the service request fuse probability value is determined based on the second ratio, for example, the second ratio is used as the service request fuse probability value, or the product of the second ratio and the preset ratio is used as the service request fuse probability value. The preset ratio can reflect the failure ratio information of the target service node for the service request within the preset statistical period, where the preset ratio can be a preset proportional coefficient less than or equal to 1, or it can be the ratio of the difference between the number of period windows and the number of consecutive successful request cycles to the number of period windows, or it can be the ratio of the number of consecutive failed request cycles to the number of period windows. For example, the service request fuse probability value can be determined by the following formula:

[0064]

[0065] or

[0066]

[0067] Where p is the service request fuse probability value, request is the number of service requests, accepts is the number of successful requests, and l is the preset ratio. This solution determines the service request fuse probability value by determining the subtraction result based on the product of the number of service requests and the target fuse sensitivity value and the number of successful requests, and by adding the number of service requests and the preset number adjustment value to obtain the second ratio of the addition result, dynamically adjusting the fuse strength, and improving the fuse effect and service reliability of the service request.

[0068] In one embodiment, the service request fuse management method provided by the present solution determines the first subtraction result based on the product of the number of service requests and the target fuse sensitivity value and the number of successful requests, which can be obtained by subtracting the number of service requests from the preset number of passage protections and the product of the target fuse sensitivity value and the number of successful requests. For example, the service request fuse probability value can be determined by the following formula:

[0069]

[0070] or

[0071]

[0072] Wherein, preserve is the number of pass protections, for example, preserve = 5. In conventional fuse solutions, when the number of service requests is small and there are request failures, the service request fuse probability value will be close to 1. This solution configures the number of pass protections. When the number of service requests is small, the service request fuse probability value will become a negative number. When the service request fuse probability value is negative, it can be directly determined that the fuse service is not needed and the first service request is directly passed, effectively improving service reliability.

[0073] In one possible embodiment, the service request fuse management method provided by the present solution determines the number of service requests for the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests through the second service request, and the number of consecutive request failure cycles. It can be determined that the number of service requests for the second service request received by the target service node corresponding to the service request within a preset statistical period, the number of successful requests through the second service request, the number of consecutive request failure cycles, and the number of consecutive request success cycles. Among them, the number of consecutive request success cycles is the number of period windows in which the response to the second service request is continuously through the second service request. Correspondingly, the service request fuse management method provided by the present solution determines the service request fuse probability value according to the second ratio, which can be a third ratio of the difference between the number of period windows and the number of consecutive request success cycles and the number of period windows; multiply the second ratio by the third ratio, and determine the multiplication result as the service request fuse probability value. For example, the service request fuse probability value provided by the present solution can be determined by the following formula:

[0074]

[0075] or

[0076]

[0077] Among them, successBarrel is the number of consecutive successful request cycles. This solution uses the third ratio of the difference between the number of cycle windows and the number of consecutive successful request cycles to the number of cycle windows as the failure ratio in the preset statistical period, and uses the multiplication result of the second ratio and the third ratio as the service request fuse probability value. The service request fuse probability value refers to the failure ratio information in the preset statistical period, which can more reasonably determine the service request fuse probability value, more accurately and dynamically adjust the fuse strength, and improve the fuse effect and service reliability of the service request.

[0078] In one embodiment, a time threshold may be configured. When the time from the current time to the last time the target service node passed the service request exceeds the time threshold, the first service request currently received may be directly passed to ensure the availability of the service.

[0079] S240: Determine whether to approve or reject the first service request according to the service request fuse probability value.

[0080] As described above, by determining the service request fuse probability value according to the number of service requests, the number of successful requests, and the number of consecutive request failure cycles of the target service node corresponding to the first service request within a preset statistical period, as well as the preset fuse sensitivity value and the number of cycle windows, and determining whether to pass or reject the first service request according to the service request fuse probability value, the fuse strength can be dynamically adjusted according to the historical response of the service node to the service request, without the need to fuse the entire service, effectively reducing the user request failure rate, and improving the service request fuse effect and service reliability. At the same time, by determining the target fuse sensitivity value according to the number of consecutive request failure cycles and the preset fuse sensitivity value and the number of cycle windows, and dynamically determining the service request fuse probability value according to the number of service requests, the number of successful requests, and the target fuse sensitivity value, the fuse strength is dynamically adjusted to improve the service request fuse effect and service reliability. Based on the splitting of a single node, when a downstream node is blown, the request will not be routed to the service node, but other node requests will be selected instead of the overall blown, so as to achieve high availability of the service, which can significantly improve the reliability and user experience of the system. In addition, through the dynamic adjustment mechanism of the blown sensitivity value based on periodic statistics, the blown probability value of the service request is dynamically adjusted according to the failure and success statistics of the service request. The blown strategy can change dynamically according to the actual request situation, avoiding misjudgment or excessive blown caused by fixed thresholds, achieving a better blown effect, and being suitable for large-scale concurrent scenarios in live events. In addition, the service request blown management can be designed modularly, and the parameters of the blown strategy can be adjusted according to actual business needs, flexibly adapting to various complex live event scenarios, and further improving the disaster recovery and scalability of the system.

[0081] Figure 4 Schematic diagram of the structure of a service request fuse management device provided by an embodiment of the present application. Figure 4 The service request fuse management device includes a request response module 41, a probability determination module 42 and a request processing module 43.

[0082] Among them, the request response module 41 is configured to, when receiving a service request, determine the number of service requests received by the target service node corresponding to the service request within a preset statistical period, the number of successful requests through the service request, and the number of consecutive request failure cycles, where the number of consecutive request failure cycles is the number of period windows in which the response mode to the service request is to reject the service request;

[0083] The probability determination module 42 is configured to determine the service request fuse probability value according to the number of service requests, the number of successful requests and the number of consecutive request failure cycles, as well as the preset fuse sensitivity value and the number of cycle windows;

[0084] The request processing module 43 is configured to determine whether to approve or reject a service request according to the service request fuse probability value.

[0085] In the above, by determining the service request fuse probability value based on the number of service requests, the number of successful requests and the number of consecutive request failure cycles of the target service node corresponding to the first service request within a preset statistical period, as well as the preset fuse sensitivity value and the number of period windows, and determining whether to pass or reject the first service request based on the service request fuse probability value, the fuse strength can be dynamically adjusted according to the historical response of the service node to the service request, without the need to fuse the entire service, effectively reducing the user request failure rate and improving the fuse effect and service reliability of the service request.

[0086] In a possible embodiment, the probability determination module 42 determines the service request fuse probability value according to the number of service requests, the number of successful requests, and the number of consecutive request failure cycles, as well as the preset fuse sensitivity value and the number of cycle windows, and is configured as follows:

[0087] Determine the target fuse sensitivity value according to the number of consecutive request failure cycles, the preset fuse sensitivity value, and the number of cycle windows;

[0088] The service request fuse probability value is determined based on the number of service requests, the number of successful requests, and the target fuse sensitivity value.

[0089] In a possible embodiment, the probability determination module 42 determines the target fuse sensitivity value according to the number of consecutive request failure cycles and the preset fuse sensitivity value and the number of cycle windows, and is configured as follows:

[0090] The difference between the preset fuse sensitivity value and the fuse sensitivity minimum threshold is multiplied by the first ratio of the number of consecutive request failure cycles and the number of cycle windows, the fuse sensitivity value is subtracted from the multiplication result, and the target fuse sensitivity value is determined according to the subtraction result.

[0091] In a possible embodiment, the probability determination module 42 subtracts the fuse sensitivity value from the multiplication result and determines the target fuse sensitivity value according to the subtraction result, and is configured as follows:

[0092] The maximum value between the subtraction result and the preset minimum fuse sensitivity threshold is determined, and the maximum value is determined as the target fuse sensitivity value.

[0093] In a possible embodiment, the probability determination module 42 determines the service request fuse probability value according to the number of service requests, the number of successful requests, and the target fuse sensitivity value, and is configured as follows:

[0094] Determine a subtraction result according to the product of the number of service requests and the target fuse sensitivity value and the number of successful requests, and add the number of service requests and the preset number adjustment value to obtain an addition result;

[0095] A second ratio of the subtraction result and the addition result is determined, and a service request fuse probability value is determined according to the second ratio.

[0096] In a possible embodiment, the probability determination module 42 determines the first subtraction result according to the product of the number of service requests and the target fuse sensitivity value and the number of successful requests, and is configured as follows:

[0097] The first subtraction result is obtained by subtracting the number of service requests from the preset number of access protections and the product of the target fuse sensitivity value and the number of successful requests.

[0098] In a possible embodiment, the probability determination module 42 determines the number of service requests of the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests of the second service request, and the number of consecutive request failure cycles, and is configured as follows:

[0099] Determine the number of service requests for the second service request received by the target service node corresponding to the service request within a preset statistical period, the number of successful requests through the second service request, the number of consecutive request failure cycles, and the number of consecutive request success cycles, where the number of consecutive request success cycles is the number of period windows in which there are consecutive responses to the second service request through the second service request;

[0100] Correspondingly, the probability determination module 42 determines the service request fuse probability value according to the second ratio, and is configured as follows:

[0101] Determine a third ratio of the difference between the number of cycle windows and the number of consecutive successful request cycles to the number of cycle windows;

[0102] The second ratio is multiplied by the third ratio, and the multiplication result is determined as the service request fuse probability value.

[0103] It is worth noting that in the embodiment of the above-mentioned service request fuse management device, the various units and modules included are divided only according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present application.

[0104] The embodiment of the present application also provides a service request fuse management device, which can integrate the service request fuse management apparatus provided in the embodiment of the present application. Figure 5 Schematic diagram of the structure of a service request fuse management device provided in an embodiment of the present application. Figure 5 The service request fuse management device includes: an input device 53, an output device 54, a memory 52 and one or more processors 51; the memory 52 is used to store one or more programs; when one or more programs are executed by one or more processors 51, the one or more processors 51 implement the service request fuse management method provided in the above embodiment. The service request fuse management device, equipment and computer provided above can be used to execute the service request fuse management method provided in any of the above embodiments, and have corresponding functions and beneficial effects.

[0105] The embodiments of the present application also provide a non-volatile storage medium storing computer executable instructions, which are used to execute the service request fuse management method provided in the above embodiments when executed by a computer processor. Of course, the non-volatile storage medium storing computer executable instructions provided in the embodiments of the present application, whose computer executable instructions are not limited to the service request fuse management method provided above, can also execute the related operations in the service request fuse management method provided in any embodiment of the present application. The service request fuse management apparatus, device and storage medium provided in the above embodiments can execute the service request fuse management method provided in any embodiment of the present application. For technical details not described in detail in the above embodiments, please refer to the service request fuse management method provided in any embodiment of the present application.

[0106] Based on the above embodiments, the embodiments of the present application also provide a computer program product. The technical solution of the present application is essentially 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. The computer program product is stored in a storage medium, including a number of instructions for enabling a computer device, a mobile terminal or a processor therein to execute all or part of the steps of the service request fuse management method provided in each embodiment of the present application.

Claims

1. A service request fuse management method, characterized in that: include: In the case of receiving a first service request, determining the number of service requests for a second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests for the second service request, and the number of consecutive request failure cycles, where the number of consecutive request failure cycles is the number of period windows in which a response to the second service request is to reject the second service request; Determine the service request fuse probability value according to the number of service requests, the number of successful requests and the number of consecutive request failure cycles, as well as the preset fuse sensitivity value and the number of cycle windows; Determine whether to approve or reject the first service request according to the service request fuse probability value.

2. The service request fuse management method according to claim 1, characterized in that: Determining the service request fuse probability value according to the number of service requests, the number of request successes, the number of consecutive request failure cycles, and a preset fuse sensitivity value and a number of cycle windows includes: Determine a target fuse sensitivity value according to the number of consecutive request failure cycles and a preset fuse sensitivity value and a number of cycle windows; The service request fuse probability value is determined according to the number of service requests, the number of successful requests and the target fuse sensitivity value.

3. The service request fuse management method according to claim 2, characterized in that: The determining a target fuse sensitivity value according to the number of consecutive request failure cycles and a preset fuse sensitivity value and a number of cycle windows includes: The difference between the preset fuse sensitivity value and the fuse sensitivity minimum threshold is multiplied by the first ratio of the number of consecutive request failure cycles and the number of cycle windows, the fuse sensitivity value is subtracted from the multiplication result, and the target fuse sensitivity value is determined according to the subtraction result.

4. The service request fuse management method according to claim 3, characterized in that: Subtracting the fuse sensitivity value from the multiplication result, and determining a target fuse sensitivity value according to the subtraction result, includes: The maximum value between the subtraction result and the preset minimum fuse sensitivity threshold is determined, and the maximum value is determined as the target fuse sensitivity value.

5. The service request fuse management method according to claim 2, characterized in that: The determining of the service request fusing probability value according to the number of service requests, the number of successful requests, and the target fusing sensitivity value includes: Determine a subtraction result according to the product of the number of service requests and the target fuse sensitivity value and the number of successful requests, and add the number of service requests and a preset number adjustment value to obtain an addition result; A second ratio of the subtraction result and the addition result is determined, and a service request fuse probability value is determined according to the second ratio.

6. The service request fuse management method according to claim 5, characterized in that: The determining a first subtraction result according to the product of the number of service requests, the target fuse sensitivity value and the number of successful requests includes: The first subtraction result is obtained by subtracting the number of service requests from the preset number of passage protections and the product of the target fuse sensitivity value and the number of successful requests.

7. The service request fuse management method according to claim 5, characterized in that: The determining the number of service requests for the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests for the second service request, and the number of consecutive request failure cycles includes: Determine the number of service requests for the second service request received by the target service node corresponding to the service request within a preset statistical period, the number of successful requests through the second service request, the number of consecutive request failure cycles, and the number of consecutive request success cycles, where the number of consecutive request success cycles is the number of period windows in which there are consecutive responses to the second service request through the second service request; Correspondingly, determining the service request fuse probability value according to the second ratio includes: Determine a third ratio of the difference between the number of cycle windows and the number of consecutive successful request cycles to the number of cycle windows; The second ratio is multiplied by the third ratio, and the multiplication result is determined as the service request fuse probability value.

8. A service request fuse management device, characterized in that: It includes a request response module, a probability determination module and a request processing module, wherein: The request response module is configured to determine, upon receiving the first service request, the number of service requests for the second service request received by the target service node corresponding to the first service request within a preset statistical period, the number of successful requests for the second service request, and the number of consecutive request failure cycles, wherein the number of consecutive request failure cycles is the number of period windows in which the response mode to the second service request is to reject the second service request; The probability determination module is configured to determine the service request fuse probability value according to the number of service requests, the number of successful requests and the number of consecutive request failure cycles, as well as a preset fuse sensitivity value and a number of cycle windows; The request processing module is configured to determine whether to approve or reject the first service request according to the service request fuse probability value.

9. A service request fuse management device, characterized in that: include: memory and one or more processors; The memory is used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the service request fuse management method as described in any one of claims 1-7.

10. A non-volatile storage medium storing computer executable instructions, characterized in that: The computer executable instructions, when executed by a computer processor, are used to execute the service request fuse management method as described in any one of claims 1-7.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the service request fuse management method described in any one of claims 1 to 7 is implemented.

Images