CN114661510A

CN114661510A - Request timeout detection method, device, equipment and storage medium

Info

Publication number: CN114661510A
Application number: CN202210306686.1A
Authority: CN
Inventors: 李国强; 刘涛
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Current assignee: Beijing Baidu Netcom Science and Technology Co Ltd
Priority date: 2022-03-25
Filing date: 2022-03-25
Publication date: 2022-06-24

Abstract

The present disclosure provides a request timeout detection method, apparatus, device and storage medium, which relate to the technical field of network communication, and in particular, to the technical field of information detection. The specific implementation scheme is as follows: continuously collecting response time length of the sent historical service request; periodically obtaining a first average response time length and a quantile value which meet a first statistical condition and are the latest response time length collected; periodically obtaining a second average response time which meets a second statistical condition and is the latest collected response time, and determining an overtime time threshold value based on the second average response time, the latest first average response time and the latest place value, wherein the second statistical condition is lower than the first statistical condition; in response to a service request sending operation, it is detected whether the sent service request is timed out based on the most recently determined timeout duration threshold. By applying the scheme provided by the embodiment of the disclosure, the accuracy of judging the overtime of the request can be improved.

Description

Request timeout detection method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of network communication technologies, and in particular, to the field of information detection technologies.

Background

With the development of software technology, the application programs, various services and other demanders may have service calling requirements to realize richer functions. After a requester sends a request to a device providing a service in order to invoke the service, it needs to detect whether the request is timed out.

Currently, it is usually detected whether the request is overtime by setting a fixed timeout duration.

Disclosure of Invention

The disclosure provides a request timeout detection method, a request timeout detection device, a request timeout detection equipment and a storage medium.

According to an aspect of the present disclosure, there is provided a request timeout detection method, including:

continuously collecting response time length of the sent historical service request;

periodically obtaining a first average response time length and a quantile value which meet a first statistical condition and are the latest response time length collected;

periodically obtaining a second average response time which meets a second statistical condition and is the latest collected response time, and determining an overtime time threshold value based on the second average response time, the latest first average response time and the latest place value, wherein the second statistical condition is lower than the first statistical condition;

in response to a service request sending operation, it is detected whether the sent service request is timed out based on the most recently determined timeout duration threshold.

According to another aspect of the present disclosure, there is provided a request timeout detecting apparatus including:

a response time length collecting module for continuously collecting the response time length of the sent historical service request;

a response duration and place value obtaining module for periodically obtaining a first average response duration and place value of the latest collected response duration which meets a first statistical condition;

a threshold determining module, configured to periodically obtain a second average response duration that meets a second statistical condition and is a response duration collected latest, and determine an timeout duration threshold based on the second average response duration, the latest first average response duration, and the latest place value, where the second statistical condition is lower than the first statistical condition;

and the overtime detection module is used for responding to the service request sending operation and detecting whether the sent service request is overtime or not based on the latest determined overtime duration threshold.

According to still another aspect of the present disclosure, there is provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the request timeout detection method described above.

According to yet another aspect of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to execute the request timeout detection method described above.

According to yet another aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the request timeout detection method described above.

As can be seen from the above, in the solution provided in the embodiment of the present disclosure, on the basis of continuously collecting the response durations of the sent historical service requests, the first average response duration, the quantile value, and the second average response duration are periodically obtained, which can ensure that the information is updated along with the sending of the service request, so that the timeout duration threshold calculated based on the second average response duration, the latest first average response duration, and the latest quantile value is also continuously updated, and the timeout duration threshold more conforms to the actual situation. On the basis, after the service request is sent, timeout detection is carried out based on the latest time timeout threshold, and the accuracy of detecting whether the service request is overtime can be improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present disclosure, nor do they limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.

Drawings

The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:

fig. 1 is a schematic flowchart of a first request timeout detection method according to an embodiment of the present disclosure;

fig. 2 is a schematic flowchart of a second request timeout detection method according to an embodiment of the present disclosure;

fig. 3 is a flowchart illustrating a third request timeout detection method according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a request timeout detection apparatus according to an embodiment of the present disclosure;

fig. 5 is a block diagram of an electronic device for implementing the request timeout detection method provided by the embodiment of the present disclosure.

Detailed Description

Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The following describes an implementation body of the solution provided by the embodiments of the present disclosure.

The execution subject of the scheme provided by the embodiment of the disclosure can be a device with a service call requirement, and can also be referred to as a machine with a service call requirement. For example, the machine having the service invocation requirement described above may be a machine that provides another service to the user. For example, the machine having the service invocation demand may be a machine that provides the service M to the user, and the machine has a demand to invoke a service such as the service N, P, Q during the work operation. Specifically, the machine having the service invocation demand may be one of a plurality of machines which have the service invocation demand in the distributed system and provide a service to the user, and for the above example, any machine which provides the service M to the user in the distributed system may be an execution subject of the solution provided in the embodiment of the present disclosure.

In addition, the functions of providing services to users and invoking services are generally implemented by software clients, so the main implementation body of the solution provided by the embodiments of the present disclosure may also be understood as: the client installed in the machine for providing services to users and calling other services may be presented in the form of SDK (Software Development Kit), LIB (library), and the like.

For convenience of description, an executive body of the scheme provided by the embodiment of the disclosure is referred to as an executive machine in the following embodiments.

The request timeout detection method provided by the embodiments of the present disclosure is described in detail below with specific embodiments.

In one embodiment of the present disclosure, referring to fig. 1, a flowchart of a first request timeout detection method is provided, which includes the following steps S101-S104.

Step S101: the response time duration of the transmitted historical service requests is collected continuously.

Because the execution machine has a service invocation demand, in order to invoke a required service, the execution machine sends a service request to a machine (hereinafter, referred to as machine a) that provides its required service, and waits for a response fed back by machine a. In order to better understand the time consumption of the execution machine in responding to each service request sent by the execution machine, the response duration of the sent service request is continuously collected in the step, because the service request is sent to the outside continuously in the whole working process of the execution machine. For example, the service request may be an SQL (Structured Query Language) request.

The historical service request is a service request sent by the execution machine.

The response time duration may be understood as a time duration from the time when the executing machine sends the service request to the time when the executing machine receives a response to the sent service request in the process of calling the required service.

In one embodiment of the disclosure, the execution machine may trigger timing after sending the historical service request each time, and end timing after obtaining a response of the historical service request, thereby obtaining a response duration of the historical service request, and forming a historical record of the response duration. In this case, when the response time length of the history service request is collected in this step, the response time length of the history service request may be collected from the formed history.

In particular, the execution machine may continuously collect the response time duration of the historical service requests through the first thread.

Step S102: and periodically obtaining a first average response time length and a quantile value of the latest collected response time length which meet the first statistical condition.

Quantile values are a statistical concept. The above-mentioned place-of-place value is one of response durations which satisfy the first statistical condition and are newly collected. In one implementation, the quantile value may be obtained according to a permutation of response durations. For example, if there are 10000 response durations, the 99.99 quantile value is: after the order of magnitude is changed, the response time length of less than 99.99% of the 10000 response time lengths is obtained. In another implementation, a small top heap may be established according to the size of each response time duration, and then the response time duration may be selected from the heap top according to the partition ratio as a partition value, for example, when the partition ratio is 99.99%, the response time duration at the heap top may be selected as the partition value.

The first statistical condition is used for selecting and calculating the first average response time length and the response time length of the quantile value. The first statistical condition may be a condition set according to different information, and the first statistical condition, the period for obtaining the first average response time length and the quantile value, and the response time lengths for calculating the first average response time length and the quantile value are described below with reference to information according to which the first statistical condition is set.

In one case, the first statistical condition may be a condition set in accordance with a time length, that is, the first statistical condition may be a condition based on a time length. For example, the first statistical condition may be that the response durations collected in the first duration are counted, so that the machine is started once every first duration, based on which the response durations used for calculating the first average response duration and the quantile value are: and correspondingly, the period for obtaining the first average response time length and the quantile value is the first time length from the time for starting statistics to the response time length collected in the first time length.

For example, the first time period may be 1 day, 10 hours, or the like.

In another case, the first statistical condition may be a condition set in accordance with the number of response periods, that is, the first statistical condition may be a condition based on the number of response periods. For example, the first statistical condition may be that a first number of collected response durations are counted, such that the execution machine may start counting once every first number of response durations are collected, based on which the response durations used for calculating the first average response duration and the quantile value are: the latest collected first number of response durations, and accordingly, the period for obtaining the first average response duration and the quantile value, is described in terms of the number of response durations, i.e., the first number described above.

For example, the first number may be 5000, 10000, or the like.

As can be seen from the above description, the execution machine may obtain the first average response duration and the quantile value according to a certain period, and since the response duration for obtaining the first average response duration and the quantile value in each period is different, the first average response duration and the quantile value are continuously changed according to the period.

In particular, the execution machine may periodically obtain the first average response time duration and the quantile value through the second thread.

Step S103: and periodically obtaining a second average response time which meets a second statistical condition and is the latest collected response time, and determining an overtime time threshold value based on the second average response time, the latest first average response time and the latest place value.

The second statistical condition is similar to the first statistical condition, the response time length for obtaining the second average response time length is similar to the response time length for obtaining the first average response time length, and the period for obtaining the second average response time length is similar to the period for obtaining the first average response time length, which will not be described in detail herein.

In addition, the second statistical condition and the first statistical condition may be set according to different information, and the information may be duration or the number of response durations. Reference may be made in detail to the following embodiments, which are not illustrated herein.

The second statistical condition is lower than the first statistical condition, and it is understood that the number of response time periods collected according to the second statistical condition is less than the number of response time periods collected according to the first statistical condition, and the second statistical condition is more easily satisfied than the first statistical condition. Reference may be made in detail to the following embodiments, which are not illustrated herein.

Specifically, the execution machine may periodically obtain the second response time via the third thread, and may determine the timeout time threshold via the fourth thread.

Step S104: in response to a service request sending operation, it is detected whether the sent service request is timed out based on the most recently determined timeout duration threshold.

In the working process of the execution machine, when a service calling requirement exists, the execution machine executes a service request sending operation so as to request services for the machine providing the required services. And responding to the operation, timing the sent service request by the execution machine, and further detecting whether the sent service request is overtime or not based on the timing duration and the latest determined overtime duration threshold.

Referring to the following embodiments, whether the service request times out may be detected in various ways, which will not be described in detail herein.

In particular, the execution machine may detect whether the service request has timed out via the fifth thread. It should be noted that the fifth thread is different from the first thread to the fourth thread, but any two threads of the first thread to the fourth thread may be the same or different, and this is not limited in the embodiment of the present disclosure.

The following exemplifies information on which the second statistical condition and the first statistical condition are set in step S103.

In one embodiment of the disclosure, the second statistical condition is the same type of condition as the first statistical condition, and in one case, the first statistical condition and the second statistical condition are both time-length-based conditions. In another case, the first statistical condition and the second statistical condition are both conditions based on the number of response periods. As can be seen from the above, the first statistical condition and the second statistical condition may be conditions set based on different information, so that when the first average response duration, the second average response duration and the quantile value are obtained, the first statistical condition and the second statistical condition can be obtained based on different statistical periods, and the applicability of the scheme provided by this embodiment is improved.

The difference between the period for obtaining the first average response duration and the place value and the period for obtaining the second average response duration when the second statistical condition is lower than the first statistical condition will be described below with reference to different information on which the statistical condition is based.

In one case, the statistical condition is a condition set according to the duration, in this case, the first statistical condition may be to count the response durations collected in the first duration, the second statistical condition may be to count the response durations collected in the second duration, the second duration is shorter than the first duration, the shorter the duration is, the smaller the response duration collected is, the easier the statistical condition is to be satisfied, and the second statistical condition is lower than the first statistical condition. Since the second duration is shorter than the first duration, the period for obtaining the second average response duration is shorter than the period for obtaining the first average response duration and the fractional value.

In another case, the statistical condition is a condition set according to the number of response durations, in which case, the first statistical condition may be to count a first number of collected response durations, the second statistical condition may be to count a second number of collected response durations, the second number is smaller than the first number, the smaller the number of response durations, the shorter the duration required for collecting the response durations, the easier the statistical condition is met, and the second statistical condition is lower than the first statistical condition. Since the second number is smaller than the first number, and the time taken to collect the second number of response durations is smaller than the time taken to collect the first number of response durations, the period for obtaining the second average response duration is shorter than the period for obtaining the first average response duration and the quantile value.

As can be seen from the above description, the period of the execution machine obtaining the second average response duration is shorter than the period of obtaining the first average response duration and the quantile value, that is, the update speed of the second average response duration is faster than the update speed of the first average response duration and the quantile value, so that the execution machine can determine the threshold value of the timeout duration with the second average response duration as the dominant, that is, the execution machine determines the threshold value of the timeout duration after obtaining the second average response duration each time based on the second average response duration obtained currently and the latest value of the first average response duration and the quantile value obtained.

For example, it is assumed that the first time period is 3 hours, the second time period is 1 hour, and the first average response time period, the place value, and the second response time period obtained at different times are as shown in table 1 below.

TABLE 1

At 1 hour

At 2 time

At 3 time

At 4 th hour

At 5 th hour

At 6 th hour

First average response time length

--

T11

--

T12

Quantile value

--

T21

--

T22

Second average response time length

T31

T32

T33

T34

T35

T36

Therefore, after calculating T33 in time 3, determining a timeout duration threshold based on T11, T21 and T33;

after calculating T34 in time 4, determining a time-out duration threshold based on T11, T21 and T34;

after T35 is obtained by calculation at time 5, determining a timeout duration threshold based on T11, T21 and T35;

after calculating T36 at time 6, a timeout period threshold is determined based on T12, T22, and T36.

A specific manner of determining the timeout period threshold is described below.

In one embodiment of the present disclosure, a ratio between a latest quantile value and a latest first average response time duration may be calculated; and obtaining the product of the proportion and the second average response time as a time-out time threshold.

Because the first average response time length and the quantile value reflect the condition that the service requested by the execution machine is responded in a longer time, and the second average response time length reflects the condition that the service requested by the execution machine is responded in a shorter time, the condition that the service requested by the execution machine is responded in a long time and a short time is taken into account when the timeout time length threshold value is obtained according to the mode, the calculated timeout time length threshold value is more consistent with the actual condition that the execution machine is responded, and the accuracy of the timeout time length threshold value is improved.

A specific implementation of detecting whether the sent service request is timed out in step S104 will be described below.

In a first implementation manner, after the execution machine sends the service request, if the first wait time exceeds the latest determined timeout time threshold, it may be directly determined that the service request sent by the execution machine is overtime. The first waiting time is as follows: the duration of waiting for a response after the execution machine sends the service request.

In a second implementation manner, if the first waiting duration of the service request sent by the execution machine exceeds the latest determined threshold of the timeout duration, the service request may be resent in a retransmission request manner, and whether the sent service request is timeout is detected based on the latest determined threshold of the timeout duration. Wherein, for the same service request, the destination device sending the service request every time is different.

For a distributed system, multiple machines often provide the same service for a user, so that when an executing machine calls a service, if a service request is sent to a first machine for improving the service and no response is received within a newly determined timeout period, a failure may occur in the first machine, at this time, the executing machine may resend the service request, and when the service request is resent, the service request is not sent to the first machine, but is sent to other machines providing the service, such as a second machine, so that the executing machine can still obtain a response in time in the case of a failure of the first machine.

Specifically, the execution device may set an upper limit of the number of times of retransmitting the service request in advance, and in this case, when the number of times of retransmitting the service request reaches the upper limit of the number of times when retransmitting the service request, the service request is not retransmitted even if the execution device does not receive a response, and it may be determined that the service request is overtime. In this case, when the total waiting time from the first time of sending the service request by the execution machine reaches the fixed time threshold, the service request is not retransmitted, and at this time, it may be determined that the service request is overtime.

The specific manner of determining the service request timeout may refer to the following steps in the embodiment of fig. 2, which will not be described in detail herein.

Corresponding to the above situation, if the first waiting time of the service request sent by the execution machine does not exceed the latest determined timeout duration threshold, which indicates that the execution machine obtains a response within the timeout duration threshold, it may be determined that the service request is not timeout.

As can be seen from the above description, when the first waiting duration of a transmitted service request exceeds the newly determined timeout duration threshold, the request timeout is not directly determined, but the request is retransmitted to a different destination device providing the same service, so that responses of multiple destination devices can be simultaneously waited for. Compared with the method that the service request is sent once and the response of only one target device is waited, the scheme provided by the embodiment can obtain the response from a plurality of target devices, and the success rate of obtaining the response is improved.

As can be seen from the foregoing description, the timeout detection for the service request may be implemented through different implementations, and the request timeout detection method provided in the embodiment of the present disclosure is described below with reference to specific implementations.

In one embodiment of the present disclosure, referring to fig. 2, a flowchart of a second request timeout detection method is provided, which includes the following steps S201-S207.

Step S201: the response time duration of the transmitted historical service requests is collected continuously.

Step S202: and periodically obtaining a first average response time length and a quantile value of the latest collected response time length which meet the first statistical condition.

Step S203: and periodically obtaining a second average response time which meets a second statistical condition and is the latest collected response time, and determining an overtime time threshold value based on the second average response time, the latest first average response time and the latest place value.

The steps S201 to S203 are the same as the steps S101 to S103, respectively, and will not be described in detail.

Step S204: in response to the service request sending operation, it is determined whether the first wait time of the sent service request exceeds the latest determined timeout time threshold, and if so, step S205 is executed.

Step S205: the transmitted service request is retransmitted.

In this step, the service request sent by the execution machine at a time is the same as the service requested by the service request sent in step S204, and the difference is only that the destination device of the service request is different.

Step S206: and judging whether the second waiting time of the retransmission service request exceeds the latest determined timeout threshold and whether the first waiting time does not exceed a preset fixed time threshold, if so, returning to execute the step S205.

The second waiting time is for each retransmission of the service request by the executing machine, that is, each retransmission of the service request corresponds to a second waiting time, and the second waiting time is a time from the retransmission of the service request to the time when the executing machine receives the response.

The fixed time threshold is generally set longer, and is usually greater than the timeout period threshold determined each time. Therefore, when one target device cannot respond to the service request of the execution machine in time, more target devices respond to the service request.

In addition, in this step, the service request is required to be retransmitted only when the first waiting time length does not exceed the fixed time length threshold, that is, the service request cannot be retransmitted any more when the first waiting time length exceeds the fixed time length threshold, so that the service request can be effectively prevented from being retransmitted indefinitely, and further the network is blocked.

Step S207: and if the first waiting time exceeds a preset fixed time threshold, judging that the sent service request is overtime.

As can be seen from the above, in the scheme provided in this embodiment, when the first waiting time exceeds the preset fixed time threshold, it is determined that the sent service request is overtime, so that an extreme case that the request is retransmitted all the time and the response is always waited for is avoided, and when the first waiting time does not exceed the preset fixed time threshold, the service request is retransmitted, and the success rate of the execution machine obtaining the response is also improved.

In an embodiment of the disclosure, the first statistical condition and the second statistical condition may be both: and counting the response time of the historical service requests of the same type.

In this case, the request timeout detection method may be implemented with reference to the steps shown in fig. 3.

Step S301: the response time duration of the transmitted historical service requests is collected continuously.

Step S301 is the same as step S101, and will not be described in detail here.

Step S302: for each type of historical service request, periodically obtaining a first average response time length and a quantile value of response time lengths of the type of historical service request which meets a first statistical condition and is collected latest.

This step is similar to step S102 in the embodiment shown in fig. 1, and the difference is only that the first average response time length and the quantile value are obtained according to the type of the historical service request, that is, when the first average response time length and the quantile value are obtained, the used response time length is the response time length of each type of the historical service request.

The specific implementation of determining whether two historical service requests are of the same type is described in the following embodiments and will not be described in detail here.

Step S303: and for each type of historical service request, periodically obtaining a second average response time which meets a second statistical condition and is the response time of the type of the newly collected historical service request, and determining an overtime time threshold of the type of the historical service request based on the second average response time, the latest first average response time of the type of the historical service request and the latest place-out value.

This step is similar to step S103 in the embodiment shown in fig. 1, and the difference is only that the second average response duration, the first average response duration, and the place value are obtained according to the type of the historical service request, that is, when the second average response duration, the first average response duration, and the place value are obtained, the used response duration is the response duration of each type of the historical service request.

In conjunction with step S302 and step S303, for each type of historical service request, the latest second average response duration, the latest first average response duration, and the quantile value can be obtained, so that the timeout duration threshold of each type of historical service request can be calculated in the same manner as that in the foregoing embodiment, and details thereof are not described here.

Step S304: and responding to the service request sending operation, obtaining the latest determined timeout duration threshold of the type of historical service request according to the type of the sent service request, and detecting whether the sent service is timeout or not based on the obtained timeout duration threshold.

In view of the above, in this embodiment, the first statistical duration, the quantile value, and the second statistical duration are obtained by taking the type of the service request as a unit, so that the condition that one type of service request obtains a response can be more accurately reflected by the timeout duration threshold determined each time. On the basis, the timeout detection is carried out on the service request according to the type of the service request, and the accuracy of the timeout detection can be improved.

A specific implementation of determining whether two historical service requests are of the same type is described below.

In one embodiment of the present disclosure, it may be determined whether two historical service requests are of the same type in the following manner:

and replacing the constant type information in the two historical service requests with preset replacement information, and determining that the two historical service requests are the same type of request if the two historical service requests after the information replacement are the same. And if the two historical service requests after the information replacement are different, determining that the two historical service requests are different types of requests.

It will be understood by those skilled in the art that the service request is generally written according to the syntax rules of the programming language used, and therefore, the information belonging to the constant type in each historical service request, for example, the number of 3, 4, 5, etc. belongs to the constant type, and the character string can also be regarded as the information belonging to the constant type, for example, 'li', etc., according to the syntax rules.

The above replacement information may be set by a developer according to a requirement, and for example, may be? | The! And the embodiments of the present disclosure do not limit this.

In one implementation, when it is determined whether the two historical service requests after information replacement are the same, the two historical service requests after information replacement can be compared character by character, and if the comparison result shows that each character in the two historical service requests after information replacement is the same, the two historical service requests are considered to be the same, otherwise, the two historical service requests are considered to be different.

For example, suppose that history service request 1 is "select abc from table where id is 3" and history service request 2 is "select abc from table where id is 4", and both history service requests query the same field in the same table, except that the query id is different. Wherein, 3and 4 are constant information, both using "? "replacement is performed by this replacement information, and the obtained post-replacement requests are all" select abc from table where id? It is obvious that the two historical service requests are the same after information replacement, and it can be determined that the two historical service requests are the same type of request. Otherwise, if the replaced requests are different, the two historical service requests are determined to be different types of requests.

Assume that the history service request 3 is "select abc from table where id is 3and name is 'li'. It can be seen that, where 3 is a number type, 'li' is a character string type, and is constant information, with? "is this replacement information replaced, and the request after replacement is" select abc from table where id? and name? ", is the request and" select abc from table where id? "by contrast, clearly with" and name? "this part of information, so it can be determined that the history server request 3 is different from the history service requests 1 and 2.

In addition, the developer may have misoperation during code writing, which may easily cause that the historical service request has information that does not cause grammar error of the service request but causes the service request to contain redundant characters.

For example, assume that historical service request 4 is:

"select abc from table where id is 3", obviously, there are a plurality of spaces between "abc" and "from", and 3 is constant information, and remove the extra spaces and use "? "after replacing the constant information, the obtained historical service request after replacing the information is: "select abc from table where id? "it is obvious that the processed history service request 4 is the same as the history service requests 1 and 2 after the replacement of the information, and therefore, it can be determined that the history service request 4 is the same as the history service requests 1 and 2.

Therefore, the replacement information is used for replacing the constant type information in the historical service request, so that the influence of the constant value of the constant type information on the judgment of the request type can be eliminated, invalid information for judging the type of the historical service request in the replaced historical service request is reduced, and the accuracy of determining the type of the historical service request can be improved.

In an embodiment of the present disclosure, referring to fig. 4, a schematic structural diagram of a request timeout detection apparatus is provided, including:

a response duration collection module 401, configured to continuously collect response durations of the sent historical service requests;

a response duration and place value obtaining module 402, configured to periodically obtain a first average response duration and place value of response durations that meet a first statistical condition and are collected latest;

a threshold determining module 403, configured to periodically obtain a second average response duration that meets a second statistical condition and is the latest collected response duration, and determine an timeout duration threshold based on the second average response duration, the latest first average response duration, and the latest place-of-value, where the second statistical condition is lower than the first statistical condition;

a timeout detection module 404, configured to detect whether the sent service request is timeout based on the latest determined timeout duration threshold in response to the service request sending operation.

As can be seen from the above, in the scheme provided in the embodiment of the present disclosure, on the basis of continuously collecting the response duration of the sent historical service request, the first average response duration, the quantile value, and the second average response duration are periodically obtained, so that it can be ensured that the information is updated along with the sending of the service request, and thus the timeout duration threshold calculated based on the second average response duration, the latest first average response duration, and the latest quantile value is also continuously updated, and the timeout duration threshold better conforms to the actual situation. On the basis, after the service request is sent, timeout detection is carried out based on the latest time timeout threshold, and the accuracy of detecting whether the service request is overtime can be improved.

In an embodiment of the present disclosure, the threshold determining module 403 includes:

a response duration unit, configured to periodically obtain a second average response duration that satisfies a second statistical condition and is a response duration that is newly collected;

a ratio calculation unit for calculating a ratio between the latest place-index value and the latest first average response time length;

a duration threshold obtaining unit, configured to obtain a product of the ratio and the second average response duration as an timeout duration threshold; wherein the second statistical condition is lower than the first statistical condition.

In an embodiment of the present disclosure, the timeout detecting module 404 is specifically configured to, in response to a service request sending operation, if a first wait time of a sent service request exceeds a latest determined timeout time threshold, resend the service request in a request retransmission manner, and detect whether the sent service request is timeout based on the latest determined timeout time threshold, where for a same service request, destination devices that send the service request each time are different.

In an embodiment of the present disclosure, the timeout detecting module 404 is specifically configured to, in response to a service request sending operation, resend the sent service request if a first wait time of the sent service request exceeds a latest determined timeout time threshold; if the second waiting time for retransmitting the service request exceeds the latest determined timeout time threshold and the first waiting time does not exceed a preset fixed time threshold, returning to the step of retransmitting the sent service request; and if the first waiting time exceeds a preset fixed time threshold, judging that the sent service request is overtime, wherein for the same service request, the target equipment for sending the service request every time is different.

In an embodiment of the present disclosure, the first statistical condition and the second statistical condition are both: and counting the response time of the historical service requests of the same type.

Since the service requests of the same type have similarity, it can be considered that the service requests of the same type also have similarity in terms of response duration and the like when the service requests of the same type are obtained. On the basis, the timeout detection is carried out on the service request according to the type of the service request, and the accuracy of the timeout detection can be improved.

In one embodiment of the present disclosure, the apparatus further comprises:

the information replacement module is used for replacing the constant type information in the two historical service requests with preset replacement information;

the same type request confirmation module is used for determining that the two historical service requests are the same type of request if the two historical service requests after information replacement are the same;

and the different-type request confirmation module is used for determining that the two historical service requests are different types of requests if the two historical service requests after information replacement are different.

In an embodiment of the present disclosure, the first statistical condition and the second statistical condition are both: a time-based condition; or both the first statistical condition and the second statistical condition are: a condition based on the number of response durations.

As can be seen from the above, the first statistical condition and the second statistical condition may be conditions set based on different information, so that when the first average response duration, the second average response duration and the quantile value are obtained, the first statistical condition and the second statistical condition can be obtained based on different statistical periods, and the applicability of the scheme provided by this embodiment is improved.

The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.

In one embodiment of the present disclosure, there is provided an electronic device including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the request timeout detection method of any one of the above method embodiments.

In one embodiment of the present disclosure, a non-transitory computer readable storage medium is provided having stored thereon computer instructions for causing a computer to perform the request timeout detection method of any one of the above method embodiments.

In an embodiment of the present disclosure, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the request timeout detection method of any of the above method embodiments.

FIG. 5 illustrates a schematic block diagram of an example electronic device 500 that can be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.

As shown in fig. 5, the apparatus 500 comprises a computing unit 501 which may perform various appropriate actions and processes in accordance with a computer program stored in a Read Only Memory (ROM)502 or a computer program loaded from a storage unit 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the device 500 can also be stored. The calculation unit 501, the ROM 502, and the RAM 503 are connected to each other by a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.

A number of components in the device 500 are connected to the I/O interface 505, including: an input unit 506 such as a keyboard, a mouse, or the like; an output unit 507 such as various types of displays, speakers, and the like; a storage unit 508, such as a magnetic disk, optical disk, or the like; and a communication unit 509 such as a network card, modem, wireless communication transceiver, etc. The communication unit 509 allows the device 500 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

The computing unit 501 may be a variety of general-purpose and/or special-purpose processing components having processing and computing capabilities. Some examples of the computing unit 501 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 501 performs the respective methods and processes described above, such as the request timeout detection method. For example, in some embodiments, the request timeout detection method may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as storage unit 508. In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 500 via the ROM 502 and/or the communication unit 509. When the computer program is loaded into the RAM 503 and executed by the computing unit 501, one or more steps of the request timeout detection method described above may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform the request timeout detection method by any other suitable means (e.g., by means of firmware).

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server may be a cloud server, a server of a distributed system, or a server combining a blockchain.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel or sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.

The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.

Claims

1. A request timeout detection method comprising:

periodically obtaining a second average response time length which meets a second statistical condition and is the latest collected response time length, and determining an overtime time length threshold value based on the second average response time length, the latest first average response time length and the latest place value, wherein the second statistical condition is lower than the first statistical condition;

2. The method of claim 1, wherein the determining a timeout duration threshold based on the second average response duration, the most recent first average response duration, and the most recent quantile value comprises:

calculating a ratio between the latest quantile value and the latest first average response time;

and obtaining the product of the proportion and the second average response time as a time-out time threshold.

3. The method of claim 1 or 2, wherein said detecting whether the transmitted service request is timed out based on a most recently determined timeout duration threshold comprises:

and if the first waiting time of the sent service request exceeds the latest determined time-out time threshold, resending the service request in a request resending mode, and detecting whether the sent service request is overtime or not based on the latest determined time-out time threshold, wherein for the same service request, target equipment for sending the service request every time is different.

4. The method of claim 3, wherein said resending the service request on demand and detecting whether the sent service request has timed out based on a newly determined timeout duration threshold comprises:

resending the sent service request;

if the second waiting time for retransmitting the service request exceeds the latest determined timeout time threshold and the first waiting time does not exceed a preset fixed time threshold, returning to the step of retransmitting the sent service request;

and if the first waiting time exceeds a preset fixed time threshold, judging that the sent service request is overtime.

5. The method of claim 1 or 2,

the first statistical condition and the second statistical condition are both: and counting the response time of the historical service requests of the same type.

6. The method of claim 5, wherein determining whether two historical service requests are of the same type is performed by:

replacing the constant type information in the two historical service requests with preset replacement information;

if the two historical service requests after information replacement are the same, determining that the two historical service requests are the same type of request;

and if the two historical service requests after the information replacement are different, determining that the two historical service requests are different types of requests.

7. The method of claim 1 or 2,

the first statistical condition and the second statistical condition are both: a time-based condition;

or

The first statistical condition and the second statistical condition are both: a condition based on the number of response durations.

8. A request timeout detection apparatus comprising:

a threshold determination module, configured to periodically obtain a second average response duration that meets a second statistical condition and is a response duration collected latest, and determine an timeout duration threshold based on the second average response duration, the latest first average response duration, and the latest place-of-value, where the second statistical condition is lower than the first statistical condition;

9. The apparatus of claim 8, wherein the threshold determination module comprises:

a duration threshold obtaining unit, configured to obtain a product of the ratio and the second average response duration as an timeout duration threshold.

10. The apparatus of claim 8 or 9,

the timeout detection module is specifically configured to, in response to a service request sending operation, resend a service request in a request retransmission manner if a first wait time of the sent service request exceeds a latest determined timeout time threshold, and detect whether the sent service request is timeout based on the latest determined timeout time threshold, where, for the same service request, destination devices that send the service request each time are different.

11. The apparatus of claim 10, wherein,

the timeout detection module is specifically configured to, in response to a service request sending operation, resend the sent service request if a first wait time of the sent service request exceeds a latest determined timeout time threshold; if the second waiting time for retransmitting the service request exceeds the latest determined timeout time threshold and the first waiting time does not exceed a preset fixed time threshold, returning to the step of retransmitting the sent service request; and if the first waiting time exceeds a preset fixed time threshold, judging that the sent service request is overtime, wherein for the same service request, the target equipment for sending the service request every time is different.

12. The apparatus of claim 8 or 9,

13. The apparatus of claim 12, wherein the apparatus further comprises:

14. The apparatus of claim 8 or 9,

or

15. An electronic device, comprising:

at least one processor; and

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.

16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.

17. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1-7.