WO2017045537A1 - Method and device for processing request in distributed system - Google Patents

Abstract

The present application discloses a method and a device for processing a request in a distributed system, the method comprises: receiving a service request initiated by a requester; according to the dimension of data operation that participates in the processing of the service request in the distributed system, dividing the service request into at least one sub-request associated with the service request; distributing the sub-request to the corresponding processing unit in the distributed system for processing; judging if the processing time of the sub-request exceeds the preset time threshold of each processing unit in the distributed system; if yes, generating an execution record of the sub-request; summarizing the execution record of the sub-request associated with the service request corresponding to the sub-request, and generating and returning the execution record of the service request to the requester. The method for processing the request in the distributed system can process a slow request more comprehensively and more efficiently, thereby improving the processing efficiency of the distributed system.

Description

Processing method and device for request in distributed system

The present application claims priority to Chinese Patent Application No. 201510582405.5, filed on Sep. 14, 2015, entitled,,,,,,,,,,,,,, in.

Technical field

The present application relates to the field of distributed system technologies, and in particular, to a processing method for a request in a distributed system. The application also relates to a processing device for requesting in a distributed system.

Background technique

With the continuous development of computer technology and network technology, the application of distributed system architecture is more and more extensive. In a distributed system, a user-initiated service request often cannot directly obtain an implementation object, and needs to perform collaborative processing on the user's service request through multiple intermediate service components, and finally completes the operation. For example, in an existing cloud computing platform, a user's simple write request for a file may require intermediate service components such as scheduling, communication, indexing, and distributed storage to complete a file write operation. These intermediate service components are generally deployed in The different processes of the server and the different software components are due to the complexity of the distributed system, which makes the performance analysis of the distributed system more difficult.

At present, the processing method of the request in the distributed system provided by the prior art includes: sampling a user request received by each server in the distributed system; generating a corresponding identifier for the user request sampled by each server, the identifier When the user requests the calling thread, the variable is passed to the current thread as a variable; the tracking interface is injected into the running process of each server in the distributed system, and when the process runs to the tracking interface, if the current process is detected, When the user requests the corresponding identifier, the identifier is associated with the related information of the function indicated by the tracking interface and generates a log; the generated logs are respectively summarized according to the corresponding identifier.

The processing method of the request in the distributed system provided by the above prior art has obvious drawbacks.

The processing method of the request in the distributed system provided by the above prior art obtains the user request as a sample from the distributed system in a sampling manner, and passes the abnormal request that affects the performance of the sample (especially the request for processing timeout, that is, Slow request) analysis to improve the performance of distributed systems, low efficiency, and flaws.

In a distributed system, slow requests are relatively small compared to all requests. In order to reduce the impact on performance, the sampling rate is low, generally one thousandth or even lower, so it is captured by sampling. Slow request ratio Less, the effect on the performance improvement of the distributed system is small; and the slow request is analyzed by collecting the log, and the adjustment made to the distributed system according to the analysis result of the slow request needs to wait for the next iteration period (log analysis period) In order to take effect, the iteration cycle is generally at the minute level (5-10 minutes), and the efficiency is low; in addition, many distributed systems applied to cloud services require capturing each slow request, which is requested in the distributed system provided by the prior art. The processing method cannot be satisfied and there are defects.

Summary of the invention

The present application provides a processing method for a request in a distributed system to solve the problems of low efficiency and drawbacks existing in the prior art.

The application also relates to a processing device for requesting in a distributed system.

The application provides a processing method for a request in a distributed system, including:

Receiving a service request initiated by the requesting party;

Dividing the service request into at least one sub-request associated with the service request according to a dimension of the data operation involved in processing the service request in the distributed system;

Distributing the sub-request to a corresponding processing unit in the distributed system for processing;

Determining whether the processing time of the sub-request exceeds a preset time threshold of each processing unit in the distributed system;

If yes, generating an execution record of the subrequest;

The execution record of the sub-request associated with the service request corresponding to the sub-request is summarized, and an execution record of the service request is generated and returned to the requester.

Optionally, the generating an execution record of the sub-request includes:

Generating an execution record of the subrequest;

Recording an execution record of the sub-request into an exception log corresponding to each of the sub-requests;

Extract a summary of the execution record of the subrequest.

Optionally, the summarizing the execution record of the sub-request associated with the service request corresponding to the sub-request, and generating the execution record of the service request and returning to the requesting party, specifically:

Summarizing a summary of execution records of the sub-requests involved in the calling link of the service request corresponding to the sub-request;

Generate a summary of the execution record of the business request;

A summary of the execution record of the business request is returned to the requestor.

Optionally, the calling link includes:

In the distributed system, the sequential combination of all servers participating in processing the service request associated subrequest.

Optionally, if the determining whether the processing time of the sub-request exceeds a time threshold step preset by the processing unit in the distributed system is no, perform the following steps:

Generating an execution record of the subrequest;

Extracting a summary of the execution record of the subrequest;

Summarizing a summary of the execution records of the subrequests;

Generate a summary of the execution record of the business request;

A summary of the execution record of the business request is returned to the requestor.

Optionally, after receiving the service request step initiated by the requesting party, and performing the data operation dimension according to the service request in the distributed system, the service request is split into at least one and the service. Before requesting the associated subrequest step, perform the following steps:

Generate an identifier that uniquely corresponds to the business request.

Optionally, the dimension participating in the data operation when processing according to the service request in the distributed system, splitting the service request into at least one sub-request step associated with the service request, and executing in the Before the sub-request is distributed to the corresponding processing unit in the distributed system for performing the processing step, the following steps are performed:

Generating an identifier corresponding to each of the sub-requests.

Optionally, the sub-request is distributed to a corresponding processing unit in the distributed system for processing, and specifically includes:

And respectively participating in the dimension of the data operation when the sub-request is processed in the distributed system, respectively sending the sub-request to a pre-set, participating in data operation when the sub-request is processed in the distributed system The processing unit corresponding to the dimension.

Optionally, after the digest substep of generating the execution record of the service request is performed, performing the following substeps:

A summary of the execution record of the service request is recorded in a log corresponding to the service request.

Optionally, the dimensions include:

Data reading, data writing, data query and data deletion.

Optionally, the association between the service request and the sub-request is determined according to an association between an identifier of the service request and an identifier of the sub-request.

Optionally, the processing unit is composed of at least one server in the distributed system.

Optionally, at least one of the following information is recorded in the execution record:

The identifier, the identity of the server participating in the processing, the processing time, the name of the function called, the time the function was called And related information generated at the time of the call.

Optionally, at least one of the following information is recorded in the summary of the execution record:

The identifier, the identity of the server participating in the processing, and the processing time.

Optionally, the exception log records an exception information generated when the function is called.

The application also provides a processing device for requesting in a distributed system, comprising:

a service request receiving unit, configured to receive a service request initiated by the requesting party;

a service request splitting unit, configured to split the service request into at least one sub-request associated with the service request according to a dimension involved in the data operation when the service request is processed in the distributed system;

a sub-request distribution unit, configured to distribute the sub-request to a corresponding processing unit in the distributed system for processing;

a sub-request judging unit, configured to determine whether a processing time of the sub-request exceeds a preset time threshold of each processing unit in the distributed system;

If yes, enter the execution record generation unit;

The execution record generating unit is configured to generate an execution record of the subrequest;

The execution record summary feedback unit is configured to summarize an execution record of the sub-request associated with the service request corresponding to the sub-request, and generate an execution record of the service request to be returned to the requesting party.

Optionally, the execution record generating unit specifically includes:

a sub-request execution record generation sub-unit for generating an execution record of the sub-request;

a sub-requesting exception logging sub-unit for recording an execution record of the sub-request into an exception log corresponding to each of the sub-requests;

A sub-request digest extraction sub-unit for extracting a summary of execution records of the sub-request.

Optionally, the performing record summary feedback unit specifically includes:

a sub-request summary summary sub-unit, configured to summarize a summary of execution records of the sub-requests involved in the invocation link of the service request corresponding to the sub-request;

a service request summary generation subunit, configured to generate a summary of an execution record of the service request;

The service request summary returns a subunit for returning a summary of the execution record of the service request to the requestor.

Optionally, if the judgment result of the sub-request judgment unit is no, the following unit is performed:

a sub-request execution record generating unit, configured to generate an execution record of the sub-request;

a sub-request summary extracting unit, configured to extract a summary of an execution record of the sub-request;

a sub-request summary summary unit for summarizing summaries of execution records of the sub-requests;

a service request summary generating unit, configured to generate a summary of an execution record of the service request;

A service request summary return unit is configured to return a summary of the execution record of the service request to the requester.

Optionally, the processing device requested in the distributed system includes:

A service request identifier generating unit is configured to generate an identifier corresponding to the service request uniquely.

Optionally, the processing device requested in the distributed system includes:

a sub-request identifier generating unit, configured to generate an identifier corresponding to each of the sub-requests.

Optionally, the sub-request distribution unit specifically includes:

a sub-request distribution sub-unit, configured to separately send the sub-request to a pre-set, and the sub-request in the distributed according to a dimension of the data operation involved in processing the sub-request in the distributed system The processing unit corresponding to the dimension participating in the data operation when processing in the system.

Compared with the prior art, the present application has the following advantages:

The method for processing a request in a distributed system provided by the present application includes: receiving a service request initiated by a requester; and participating in a data operation dimension in processing in the distributed system according to the service request, splitting the service request into at least one The service requests the associated sub-request; the sub-request is distributed to a corresponding processing unit in the distributed system for processing; and it is determined whether the processing time of the sub-request exceeds a preset of the processing unit in the distributed system a time threshold; if yes, generating an execution record of the sub-request; summarizing an execution record of the sub-request associated with the service request corresponding to the sub-request, and generating an execution record of the service request to be returned to the requesting party.

The processing method of the request in the distributed system provided by the present application sets a corresponding time threshold for the processing unit in the distributed system, and filters out the sub-request with the processing time exceeding the corresponding time threshold by the time threshold in the processing unit, that is, the slow request In order to capture all the slow requests in the distributed system, and obtain the execution record of the service request according to the execution record summary of the sub-request, and return the execution record of the service request to the requesting party, and the processing of the slow request is more comprehensive and more efficient. At the same time, the processing efficiency of the distributed system is improved.

DRAWINGS

1 is a process flow diagram of an embodiment of a processing method of a request in a distributed system provided by the present application;

2 is a schematic diagram of an embodiment of a processing device requested in a distributed system provided by the present application.

detailed description

Numerous specific details are set forth in the description below in order to provide a thorough understanding of the application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can do not violate the meaning of the present application. A similar promotion is made, and thus the application is not limited by the specific implementations disclosed below.

The present application provides a processing method for a request in a distributed system, and the present application further provides a processing device for requesting in a distributed system, which is described in detail below with reference to the accompanying drawings of the embodiments provided herein, and Each step is explained.

The processing method for requesting in a distributed system provided by the present application is as follows:

Referring to Figure 1, there is shown a process flow diagram of an embodiment of a processing method of a request in a distributed system provided by the present application. Furthermore, the relationship between the various steps of the processing method embodiment of the request in the distributed system is determined according to FIG.

Step S101: Receive a service request initiated by the requesting party.

For distributed systems, an important factor affecting their performance is the number of exception requests, especially the number of slow requests. Once the number of slow requests in a distributed system is too large, the processing performance of the distributed system is greatly reduced. In order to improve the processing efficiency of distributed systems, it is necessary to analyze the reasons for the existence of slow requests in distributed systems. However, due to the complexity of distributed systems, it is difficult to track and locate slow requests. In this case, using the processing method of the request in the distributed system provided by the present application, on the basis of fully considering the characteristics of the distributed system, all the slow requests in the distributed system are captured by setting the time threshold, and the slow The requested execution record can accurately locate the slow request, thereby analyzing the cause of the slow request, and correspondingly processing in real time to improve the processing efficiency of the distributed system.

The requesting party refers to a user of a distributed system, such as a user who uses or rents an Open Structured Data Service (OTS). Open Structured Data Service (OTS) is a multi-tenant cloud service that provides cloud services to users. Rent a business. The service request refers to a user-initiated user request in a distributed system.

In general, in a distributed system, there are multiple subsystems, each of which acts as a processing unit for processing business requests. If a service request involves more types of data operations, when the service request is processed in a distributed system, it may be split into multiple sub-requests, which are respectively processed by corresponding processing units in the distributed system. For example, if the service request involves data reading, it is processed by a processing unit dedicated to data reading in the distributed system; and if the service request involves data writing, data query, and data deletion, the operation is performed in a distributed system. When processed, it is split into three sub-requests, which are processed by processing units for data writing, data query, and data deletion in the distributed system.

It should be noted that the processing unit in the distributed system is composed of servers in a distributed system, and each subsystem includes at least one server.

In the specific implementation, each service request has a unique corresponding identifier, such as for each service request With a unique corresponding ID.

Correspondingly, the sub-requests also have respective corresponding identifiers, such as respectively assigning IDs for sub-requests.

In a distributed system, sub-requests are obtained by splitting according to service requests. Therefore, there is an association relationship between service requests and sub-requests. Preferably, the association between the service request and the sub-request is determined according to an association relationship between an identifier of the service request and an identifier of the sub-request. For example, if the ID corresponding to the service request is 201508070024, the ID corresponding to the sub-request associated with the service request may be set to 201508070001_1, 201508070001_2, . . . , 201508070001_x, or 20150807000101, 20150807000102, . . . , 201508070001x.

The time threshold is used to filter the slow request in the distributed system. When the service request or the sub-request is processed in the distributed system, once the service request or the sub-request is processed, the processing time is exceeded. The pre-set time threshold, then the service request or the sub-request is determined to be a slow request, and vice versa.

Preferably, after the step is performed, that is, after receiving the service request initiated by the requesting party, performing the step of generating an identifier corresponding to the service request uniquely.

Step S102: Participate in a dimension of the data operation according to the service request in the distributed system, and split the service request into at least one sub-request associated with the service request.

In a distributed system, the dimension of the service request participating in the data operation when processed in the distributed system refers to the type of data operation involved when the service request is processed in the distributed system. Preferably, the dimensions include: data reading, data writing, data query, and data deletion; in a specific implementation, the dimension may also include other types of data operations, which are not limited herein.

In this step, according to the dimension of the data operation involved in processing the service request in the distributed system, the service request is split into at least one sub-request associated with the service request, and the sub-request is distributed by the system. The corresponding processing unit in the process is processed.

Preferably, after the step is performed, after the service request is split into at least one sub-request associated with the service request, the step of generating an identifier corresponding to each of the sub-requests is performed.

Step S103, distributing the sub-request to a corresponding processing unit in the distributed system for processing.

According to the above step S101, in the distributed system, the processing unit is set according to the dimension of the data operation when the service request is processed in the distributed system, for example, the service request participates in processing in the distributed system. Data operations dimensions such as data reading, data writing, data query, and data deletion are set in a distributed system for processing processing units involving data reading, data writing, data query, and data deletion;

According to the above step S102, in the distributed system, the service request is distributed according to the service request. The dimension involved in the data operation during processing is split into at least one sub-request associated with the service request;

It can be seen that the dimensions of the two are consistent with each other, that is, the service request is split according to the processing unit in the distributed system, and split into at least one sub-request for processing in the corresponding processing unit.

In a specific implementation, for some special service requests, when processing in a distributed system involves only one dimension of data operation, a sub-request corresponding to each type of service request may be generated.

In this embodiment, the sub-request is distributed to a corresponding processing unit in the distributed system for processing.

Preferably, the sub-requests are respectively sent to the pre-set and the sub-requests are processed in the distributed system when the sub-requests are processed in the distributed system. The processing unit corresponding to the dimension of the data operation.

Step S104: Determine whether the processing time of the sub-request exceeds a preset time threshold of the processing unit in the distributed system.

In this embodiment, in order to filter all the slow requests in the distributed system, a corresponding time threshold is preset for each processing unit in the distributed system.

The time threshold is a time threshold set in advance for a processing unit in a distributed system. Correspondingly, when the sub-request associated with the service request is processed by each processing unit of the distributed system, once the processing time of the sub-request in any one of the processing units of the distributed system exceeds a preset time threshold of the processing unit, The subrequest is determined to be a slow request, and vice versa.

In a specific implementation, a corresponding time threshold may be preset for each server in the processing unit. When the processing request associated with the sub-request of the server exceeds the preset time threshold of the server, the service request or the The subrequest is determined to be a slow request, and vice versa.

In addition, in a specific implementation, a time threshold set in advance for the processing unit in the distributed system may be dynamically adjusted.

In this embodiment, it is determined whether the processing time of the sub-request exceeds a time threshold set by each of the processing units in the distributed system;

If so, the following steps S105 and S106 are performed.

Step S105, generating an execution record of the subrequest.

This step and the following step S105 are implemented. In the above step S104, it is determined whether the processing time of the sub-request exceeds the preset time threshold of the processing unit in the distributed system, that is, the determination is The subrequest is a slow request. In this embodiment, for the slow request in the distributed system, in combination with this step and the following step S105, an execution record of the slow request (ie, the subrequest) is generated, and the service request association corresponding to the slow request is summarized. An execution record of the child request, and an execution record of the generated business request is returned to the requester.

The execution record refers to the detailed information when executed in a distributed system. Preferably, the execution record records at least one piece of information: an identifier, an identifier of a server participating in the processing, a processing time, a function name of the call, a time of calling the function, and related information generated when the call is made.

For example, the execution information of a subrequest in a distributed system is:

201508070001_1;

A1, a2, a3;

1s, 2s, 1s;

Read();

Xx:xx:xx;

Xxxx.

Where 201508070001_1 refers to the identifier (ID) of the sub-request;

A1, a2, a3, refer to an identifier (ID) of a server participating in processing the sub-request in the distributed system;

1s, 2s, 1s, refers to the time taken to process the servers at a1, a2, and a3 respectively;

Read() refers to the name of the function being called;

Xx:xx:xx, refers to the time point when the function is called;

Xxxx is the result of a function call, that is, the related information generated when the function is called.

In the specific implementation, other information than the foregoing information may be recorded in the execution record, which is not limited herein.

Preferably, in a specific implementation, the step specifically includes the following three sub-steps:

1) generating an execution record of the subrequest;

That is, an execution record of the slow request (ie, a subrequest) described above is generated.

2) recording an execution record of the subrequest to an exception log corresponding to each of the subrequests;

In a distributed system, any slow request has its own corresponding exception log. The abnormality log is used to record an execution record of a slow request.

Preferably, the exception log records an exception information generated when the function is called, such as an exception log of the JAVA function.

3) Extract a summary of the execution record of the subrequest.

In the distributed system, by extracting the summary of the execution record of the slow request, compared with the execution record, on the one hand, the performance loss when performing corresponding data processing in the distributed system can be reduced; on the other hand, the distribution can be reduced. The network bandwidth occupied by the system and the requester.

Preferably, at least one piece of information is recorded in the summary of the execution record: an identifier, an identifier of a server participating in the processing, and a processing time.

For example, the summary of the execution record of the extracted subrequest is:

201508070001_1;

A1, a2, a3;

1s, 2s, 1s.

Where 201508070001_1 refers to the identifier (ID) of the sub-request;

A1, a2, a3, refer to an identifier (ID) of a server participating in processing the sub-request in the distributed system;

1s, 2s, and 1s refer to the length of time spent on processing at the a1, a2, and a3 servers.

In a specific implementation, other information in the execution record may also be used as a digest, as long as it can be ensured that the slow request can be located by the digest or the reason for the slow request can be analyzed.

Step S106, the execution record of the sub-request associated with the service request corresponding to the sub-request is summarized, and an execution record of the service request is generated and returned to the requesting party.

In this step, the execution record of all the sub-requests associated with the service request corresponding to the slow request is summarized, and the execution record of the service request is returned to the requesting party. After receiving the execution record of the service request, the requesting party may perform the record according to the execution record. Troubleshoot the problem and determine whether it is a code problem, a network problem, or a distributed system problem. If it is a distributed system problem, you can get a corresponding solution by feeding back to the administrator of the distributed system.

In this embodiment, if any one of the sub-requests in the distributed system is determined to be a slow request, the execution record of all the sub-requests associated with the service request corresponding to the slow request is summarized, and an execution record of the service request is generated and returned to the The requesting party is very helpful in analyzing and locating the slow request by the requesting party.

In the above step S105, based on the summary of the execution record of the sub-request, preferably, the step specifically includes the following three sub-steps:

1) summary of the execution record of the sub-request involved in the calling link of the service request corresponding to the sub-request;

The role of the invoking link is to determine the location of the sub-request associated with the service request in the distributed system, thereby acting as a "location".

Preferably, the calling link refers to a sequential combination of all servers in the distributed system that participate in processing the service request associated sub-request.

For example, there are two sub-requests for a service request: sub-request A and sub-request B. When sub-request A is processed in a distributed system, the servers participating in processing the request A have a1, a2, and a3, and sub-request A Distributed The calling link in the system (the sequential combination of all the servers participating in the processing of the sub-request) is: a1->a2->a3, or (a1, a2, a3); correspondingly, the sub-request B is in the distributed system The processing link is: c1->c2->c3, or (c1, c2, c3); the calling link of the service request is: a1->a2->a3, c1->c2->c3, or (a1) , a2, a3; c1, c2, c3).

2) generating a summary of the execution record of the business request;

Preferably, after the step is executed, that is, after generating the digest of the execution record of the service request, performing a sub-step of recording the summary of the execution record of the service request to the log corresponding to the service request.

3) Return a summary of the execution record of the business request to the requesting party.

That is, if any one of the sub-requests in the distributed system is determined to be a slow request, the summary of the execution record of the sub-request involved in the invocation link of the service request corresponding to the slow request is summarized, and an execution record of the service request is generated. And returned to the requestor.

Preferably, in a specific implementation, in the foregoing step S104, if it is determined whether the processing time of the sub-request exceeds a time threshold set by each of the processing units in the distributed system, the determination result is no, that is, the sub-request Instead of a slow request, perform the following steps:

Generating an execution record of the subrequest;

Extracting a summary of the execution record of the subrequest;

Summarizing a summary of the execution records of the subrequests;

Generate a summary of the execution record of the business request;

A summary of the execution record of the business request is returned to the requestor.

In a specific implementation, the summary of the execution record of the service request may also be summarized and generated according to the calling link of the service request.

In addition, in a specific implementation, if it is determined whether the processing time of the sub-request exceeds a time threshold set by each of the processing units in the distributed system, the sub-request is not a slow request, except the above steps. In addition, other processing may be performed on the sub-request or the service request, or no processing is performed, which is not limited thereto.

In summary, the processing method of the request in the distributed system provided by the present application sets a corresponding time threshold for the processing unit in the distributed system, and filters out the processing time beyond the corresponding time threshold by using the time threshold in the processing unit. The request, that is, the slow request, captures all the slow requests in the distributed system, and the execution records of each slow request are recorded in the corresponding exception logs, and are not missed, and the execution record of the service request is recorded to the corresponding In the log, the information collected for slow requests is more complete, and the analysis of the location and cause of slow requests Provided convenience; in addition, according to the execution record of the sub-request, the execution record of the service request is obtained, and the execution record of the service request is returned to the requesting party, and the processing of the slow request is more comprehensive and more efficient, and the distributed system is improved. Processing efficiency.

The processing device requested in a distributed system provided by the present application is implemented as follows:

In the above embodiments, a processing method for a request in a distributed system is provided. Correspondingly, the present application further provides a processing device for requesting in a distributed system, which will be described below with reference to the accompanying drawings.

Referring to Figure 2, there is shown a schematic diagram of an embodiment of a processing device requested in a distributed system provided by the present application.

Since the device embodiment is basically similar to the method embodiment, the description is relatively simple. For related parts, refer to the corresponding description of the method embodiment provided above. The device embodiments described below are merely illustrative.

The application provides a processing device for requesting in a distributed system, including:

The service request receiving unit 201 is configured to receive a service request initiated by the requesting party;

The service request splitting unit 202 is configured to split the service request into at least one sub-request associated with the service request according to the dimension of the data operation participating in processing in the distributed system according to the service request;

a sub-request distribution unit 203, configured to distribute the sub-request to a corresponding processing unit in the distributed system for processing;

The sub-request judging unit 204 is configured to determine whether the processing time of the sub-request exceeds a preset time threshold of each of the processing units in the distributed system;

If yes, enter the execution record generation unit 205;

The execution record generating unit 205 is configured to generate an execution record of the subrequest;

The execution record summary feedback unit 206 is configured to summarize execution records of the sub-requests associated with the service request corresponding to the sub-request, and generate an execution record of the service request to be returned to the requesting party.

Optionally, the execution record generating unit 205 specifically includes:

a sub-request execution record generation sub-unit for generating an execution record of the sub-request;

a sub-requesting exception logging sub-unit for recording an execution record of the sub-request into an exception log corresponding to each of the sub-requests;

A sub-request digest extraction sub-unit for extracting a summary of execution records of the sub-request.

Optionally, the execution record summary feedback unit 206 specifically includes:

a sub-request summary summary sub-unit, configured to summarize a summary of execution records of the sub-requests involved in the invocation link of the service request corresponding to the sub-request;

a service request summary generation subunit, configured to generate a summary of an execution record of the service request;

The service request summary returns a subunit for returning a summary of the execution record of the service request to the requestor.

Optionally, the calling link includes:

In the distributed system, the sequential combination of all servers participating in processing the service request associated subrequest.

Optionally, if the judgment result of the sub-request determination unit 204 is no, the following unit is entered:

a sub-request execution record generating unit, configured to generate an execution record of the sub-request;

a sub-request summary extracting unit, configured to extract a summary of an execution record of the sub-request;

a sub-request summary summary unit for summarizing summaries of execution records of the sub-requests;

a service request summary generating unit, configured to generate a summary of an execution record of the service request;

A service request summary return unit is configured to return a summary of the execution record of the service request to the requester.

Optionally, the processing device requested in the distributed system includes:

A service request identifier generating unit is configured to generate an identifier corresponding to the service request uniquely.

Optionally, the processing device requested in the distributed system includes:

a sub-request identifier generating unit, configured to generate an identifier corresponding to each of the sub-requests.

Optionally, the sub-request distribution unit 203 specifically includes:

a sub-request distribution sub-unit, configured to separately send the sub-request to a pre-set, and the sub-request in the distributed according to a dimension of the data operation involved in processing the sub-request in the distributed system The processing unit corresponding to the dimension participating in the data operation when processing in the system.

Optionally, the processing device requested in the distributed system includes:

The record recording log unit is configured to record a summary of the execution record of the service request into a log corresponding to the service request.

Optionally, the dimensions include:

Data reading, data writing, data query and data deletion.

Optionally, the association between the service request and the sub-request is determined according to an association between an identifier of the service request and an identifier of the sub-request.

Optionally, the processing unit is composed of at least one server in the distributed system.

Optionally, at least one of the following information is recorded in the execution record:

The identifier, the identity of the server participating in the processing, the processing time, the name of the function being called, the time the function was called, and related information generated at the time of the call.

Optionally, at least one of the following information is recorded in the summary of the execution record:

The identifier, the identity of the server participating in the processing, and the processing time.

Optionally, the exception log records an exception information generated when the function is called.

The present application is disclosed in the above preferred embodiments, but it is not intended to limit the present application, and any person skilled in the art can make possible changes and modifications without departing from the spirit and scope of the present application. The scope of protection should be based on the scope defined by the claims of the present application.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory. Memory is an example of a computer readable medium.

1. Computer readable media including both permanent and non-persistent, removable and non-removable media may be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media, such as modulated data signals and carrier waves.

2. Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Claims (22)

A processing method for a request in a distributed system, comprising: Receiving a service request initiated by the requesting party; Dividing the service request into at least one sub-request associated with the service request according to a dimension of the data operation involved in processing the service request in the distributed system; Distributing the sub-request to a corresponding processing unit in the distributed system for processing; Determining whether the processing time of the sub-request exceeds a preset time threshold of each processing unit in the distributed system; If yes, generating an execution record of the subrequest; The execution record of the sub-request associated with the service request corresponding to the sub-request is summarized, and an execution record of the service request is generated and returned to the requester. The processing method of the request in the distributed system according to claim 1, wherein the generating the execution record of the sub-request comprises: Generating an execution record of the subrequest; Recording an execution record of the sub-request into an exception log corresponding to each of the sub-requests; Extract a summary of the execution record of the subrequest. The method for processing a request in a distributed system according to claim 2, wherein the execution record of the sub-request associated with the service request corresponding to the sub-request is summarized, and an execution record of the service request is generated and returned to the request Party, specifically including: Summarizing a summary of execution records of the sub-requests involved in the calling link of the service request corresponding to the sub-request; Generate a summary of the execution record of the business request; A summary of the execution record of the business request is returned to the requestor. The method for processing a request in a distributed system according to claim 3, wherein the calling link comprises: In the distributed system, the sequential combination of all servers participating in processing the service request associated subrequest. The method for processing a request in a distributed system according to claim 1, wherein the determining whether the processing time of the sub-request exceeds a step of a time threshold preset by each processing unit in the distributed system If the result is no, perform the following steps: Generating an execution record of the subrequest; Extracting a summary of the execution record of the subrequest; Summarizing a summary of the execution records of the subrequests; Generate a summary of the execution record of the business request; A summary of the execution record of the business request is returned to the requestor. The method for processing a request in a distributed system according to claim 1, wherein said step of receiving a service request initiated by a requesting party is performed, and participating in data when said processing in said distributed system according to said service request The dimension of the operation, before splitting the business request into at least one sub-request step associated with the service request, perform the following steps: Generate an identifier that uniquely corresponds to the business request. The processing method for requesting in a distributed system according to claim 1, wherein the dimension of the data operation is divided according to the service request in the distributed system, and the service request is split into at least one After the sub-request step associated with the service request is performed, and before the sub-request is distributed to the corresponding processing unit in the distributed system for processing step execution, the following steps are performed: Generating an identifier corresponding to each of the sub-requests. The processing method of the request in the distributed system according to claim 1, wherein the distributing the sub-request to the corresponding processing unit in the distributed system for processing, specifically includes: And respectively participating in the dimension of the data operation when the sub-request is processed in the distributed system, respectively sending the sub-request to a pre-set, participating in data operation when the sub-request is processed in the distributed system The processing unit corresponding to the dimension. The method for processing a request in a distributed system according to claim 3 or 5, wherein after the step of generating the digest of the execution record of the service request is performed, the following sub-steps are performed: A summary of the execution record of the service request is recorded in a log corresponding to the service request. The processing method of a request in a distributed system according to claim 1, wherein the dimension comprises: Data reading, data writing, data query and data deletion. The processing method for a request in a distributed system according to claim 1, wherein the association between the service request and the sub-request is based on an association between an identifier of the service request and an identifier of the sub-request Relationship is determined. The processing method of a request in a distributed system according to claim 1, wherein the processing unit is composed of at least one server in the distributed system. A processing method for a request in a distributed system according to claim 1, wherein said performing At least one of the following information is recorded in the record: The identifier, the identity of the server participating in the processing, the processing time, the name of the function being called, the time the function was called, and related information generated at the time of the call. The processing method of a request in a distributed system according to claim 2, 3 or 5, characterized in that at least one of the following information is recorded in the summary of the execution record: The identifier, the identity of the server participating in the processing, and the processing time. The processing method of a request in a distributed system according to claim 2, wherein the abnormality log records an abnormality information generated when the function is called. A processing device for requesting in a distributed system, comprising: a service request receiving unit, configured to receive a service request initiated by the requesting party; a service request splitting unit, configured to split the service request into at least one sub-request associated with the service request according to a dimension involved in the data operation when the service request is processed in the distributed system; a sub-request distribution unit, configured to distribute the sub-request to a corresponding processing unit in the distributed system for processing; a sub-request judging unit, configured to determine whether a processing time of the sub-request exceeds a preset time threshold of each processing unit in the distributed system; If yes, enter the execution record generation unit; The execution record generating unit is configured to generate an execution record of the subrequest; The execution record summary feedback unit is configured to summarize an execution record of the sub-request associated with the service request corresponding to the sub-request, and generate an execution record of the service request to be returned to the requesting party. The processing device of the request in the distributed system according to claim 16, wherein the execution record generating unit specifically includes: a sub-request execution record generation sub-unit for generating an execution record of the sub-request; a sub-requesting exception logging sub-unit for recording an execution record of the sub-request into an exception log corresponding to each of the sub-requests; A sub-request digest extraction sub-unit for extracting a summary of execution records of the sub-request. The apparatus for processing a request in a distributed system according to claim 17, wherein the performing the record summary feedback unit comprises: a sub-request summary summary sub-unit, configured to summarize a summary of execution records of the sub-requests involved in the invocation link of the service request corresponding to the sub-request; a service request summary generation subunit, configured to generate a summary of an execution record of the service request; The service request summary returns a subunit for returning a summary of the execution record of the service request to the requestor. The processing device of the request in the distributed system according to claim 16, wherein if the judgment result of the sub-request determination unit is negative, the following unit is performed: a sub-request execution record generating unit, configured to generate an execution record of the sub-request; a sub-request summary extracting unit, configured to extract a summary of an execution record of the sub-request; a sub-request summary summary unit for summarizing summaries of execution records of the sub-requests; a service request summary generating unit, configured to generate a summary of an execution record of the service request; A service request summary return unit is configured to return a summary of the execution record of the service request to the requester. The processing device of the request in the distributed system according to claim 16, comprising: A service request identifier generating unit is configured to generate an identifier corresponding to the service request uniquely. The processing device of the request in the distributed system according to claim 16, comprising: a sub-request identifier generating unit, configured to generate an identifier corresponding to each of the sub-requests. The processing device of the request in the distributed system according to claim 16, wherein the sub-request distribution unit specifically includes: a sub-request distribution sub-unit, configured to separately send the sub-request to a pre-set, and the sub-request in the distributed according to a dimension of the data operation involved in processing the sub-request in the distributed system The processing unit corresponding to the dimension participating in the data operation when processing in the system.

Images