WO2019149032A1 - Distributed transaction processing method and device - Google Patents

Abstract

A distributed transaction processing method and device. In the distributed transaction processing method, a transaction manager obtains a plurality of branch transactions of a distributed transaction (S410); the plurality of branch transactions is parsed to determine respective processing objects of the plurality of branch transactions and processing modes of resources corresponding to the processing objects (S420); the dependency relationship between the plurality of branch transactions is determined according to the processing objects and the processing modes (S430); and the plurality of branch transactions is processed in parallel and/or in series according to the dependency relationship (S440).

Description

Distributed transaction processing method and device Technical field

One or more embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a distributed transaction processing method and apparatus.

Background technique

In the traditional technology, in the process of processing distributed transactions, in order to ensure the consistency of each participant, the Transaction Manager (TM) usually calls each participant to process the corresponding branch transaction in a serial manner. As shown in Figure 1, TM handles distributed transactions through two phases: the preprocessing phase and the commit or rollback phase. In the pre-processing phase, TM will try to lock resources in Resource Manager (RM) 1 (an independent participant in a distributed environment), and if successful, try to consult and lock RM2 (distributed environment) If the resources in another independent participant are successful, they will enter the submission phase. In the commit phase, the TM initiates a transaction commit operation, releases the resources locked in the pre-processing phase in RM1, and performs resource consumption processing. After successful, the resource release and actual consumption of RM2 are continued. In the above submission process, if there is any abnormality, the TM will continue to retry the submission until it is successful. It can be understood that if there is a failure in the pre-processing stage, a rollback is initiated, and the TM will only finish the transaction after the RM1 and RM2 rollbacks are successfully answered, otherwise the rollback will be continuously re-tried until it succeeds.

Therefore, there is a need to provide a solution for handling distributed transactions more efficiently.

Summary of the invention

One or more embodiments of the present specification describe a distributed transaction processing method and apparatus that can improve the processing efficiency of distributed transactions.

In a first aspect, a distributed transaction processing method is provided, comprising:

The transaction manager obtains multiple branch transactions corresponding to the distributed transaction;

Parsing the plurality of branch transactions to determine respective processing objects of the plurality of branch transactions and processing manners of resources corresponding to the processing objects;

Determining a dependency relationship between the plurality of branch transactions according to the processing object and the processing manner;

The plurality of branch transactions are processed in parallel and/or serially according to the dependency.

In a second aspect, a distributed transaction processing apparatus is provided, including:

An obtaining unit, configured to acquire multiple branch transactions corresponding to the distributed transaction;

a parsing unit, configured to parse the plurality of branch transactions acquired by the acquiring unit to determine a processing object of each of the plurality of branch transactions and a processing manner of resources corresponding to the processing object;

a determining unit, configured to determine a dependency relationship between the plurality of branch transactions according to the processing object parsed by the parsing unit and the processing manner;

And a processing unit, configured to process the plurality of branch transactions in parallel and/or serial according to the dependency determined by the determining unit.

The distributed transaction processing method and apparatus provided by one or more embodiments of the present specification, the transaction manager acquires a plurality of branch transactions of a distributed transaction. A plurality of branch transactions are analyzed to determine respective processing objects of the plurality of branch transactions and processing of resources corresponding to the processing objects. Depending on the processing object and the processing method, the dependencies between multiple branch transactions are determined. According to this dependency, multiple branch transactions are processed in parallel and/or serially. Thereby, the processing efficiency of the distributed transaction can be improved.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present specification, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present specification, Those skilled in the art can also obtain other drawings based on these drawings without any creative work.

1 is a schematic diagram of a conventional distributed transaction processing method;

2 is an information interaction diagram of a distributed transaction processing method;

FIG. 3 is a schematic diagram of an application scenario of a distributed transaction processing method according to an embodiment of the present disclosure;

4 is a flowchart of a distributed transaction processing method provided by an embodiment of the present specification;

FIG. 5 is a schematic diagram of a distributed transaction processing apparatus according to an embodiment of the present disclosure.

Detailed ways

Before introducing the scheme provided in this manual in detail, the following optimization ideas are given in combination with the traditional technology:

The information interaction diagram of the distributed transaction processing method shown in FIG. 1 can be as shown in FIG. 2. As can be seen from Figure 2, during the pre-processing phase, the transaction manager has essentially no dependencies on the calls to individual participants. In addition, there is no necessary dependency on the above calling process, either in the commit phase or in the rollback phase. Therefore, in a distributed environment, the transaction manager can make calls to each participant in a concurrent manner. That is, each branch transaction can be processed in parallel. In the above parallel manner, the more time there are participants, the time of distributed transaction processing does not increase linearly. For example, if the service interaction time is T, and there are N participants, if the traditional distributed transaction processing is adopted, the processing overhead of both phases is NT. In parallel, the processing time can be basically guaranteed to be T.

The solution provided in this specification is described in detail below in conjunction with the above optimization ideas.

The distributed transaction processing method provided by one embodiment of the present specification can be applied to the scenario shown in FIG. 3. In FIG. 3, the service system is configured to divide the distributed transaction into multiple branch transactions according to the service request. A branch transaction here can refer to a behavior of a distributed transaction. For example, the business requirement is: "Transfer 100 yuan from account A to account B". For example, the distributed transaction can be divided into two branch transactions, which are used for the following processing: "A-100 "and "B+100". The business system can then send the divided multiple branch transactions to the transaction manager. After receiving the plurality of branch transactions, the transaction manager may parse the plurality of branch transactions to determine respective processing objects (eg, accounts, etc.) and resources corresponding to the processing objects (eg, account balance, gold, etc.) ). After that, the dependencies between the multiple branch transactions can be determined according to the processing object and the processing manner. And according to the dependency, multiple branch transactions are processed in parallel and/or serially. Finally, the transaction manager returns the processing result information of the multiple branch transactions to the business system.

It should be noted that, in FIG. 3, the transaction manager specifically processes the branch transaction by calling the participant, wherein the participant may refer to the service invoked by the transaction manager when processing the branch transaction. As in the previous example, one participant can be considered a financial library A and another participant can be considered a financial library B. Specifically, in the processing of the above two branch transactions, the transaction manager can call the financial library A to transfer 100 yuan from the account A, and can call the financial library B to transfer the account B to 100 yuan. Thus, the consistency of account A deduction and account B replenishment is guaranteed. During the processing of the above branch transaction, if there is any exception, the rollback fails and the feedback fails.

4 is a flow chart of a distributed transaction processing method provided by an embodiment of the present specification. The execution entity of the method can be the transaction manager of Figure 3. As shown in FIG. 4, the method may specifically include:

In step 410, the transaction manager obtains multiple branch transactions corresponding to the distributed transaction.

In one implementation, the business system can divide the distributed transaction into multiple branch transactions according to business requirements. The business needs are: "Transfer 100 yuan from account A to account B, and 5 yuan from account B to account C". For example, the distributed transaction can be divided into four branch transactions, the four branch transactions. They are used for the following processes: "A-100", "B+100", "B-5", and "C+5". The business system can then send the divided multiple branch transactions to the transaction manager.

Step 420: Parse a plurality of branch transactions to determine a processing object of each of the plurality of branch transactions and a processing manner of the resource corresponding to the processing object.

The processing object here may include a user's account or the like. The resources corresponding to the processing object may include, but are not limited to, account balance (also referred to as funds), gold, and the like. The processing method of the resource corresponding to the processing object may include resource increase, resource consumption, and the like. For example, if the processing object is an account and the resource corresponding to the processing object is an account balance, the processing method of the resource may be determined according to the increase or decrease of the account balance of the account. Specifically, when the account balance in the account is increased, the processing of the resource may be a resource increase; and when the account balance in the account is reduced, the processing of the resource may be resource consumption.

As in the foregoing example, the respective processing objects of the four branch transactions are: "Account A", "Account B", "Account B", and "Account C". In addition, since the first branch transaction is used to deduct 100 yuan from the account balance of account A, that is, the first branch transaction is used to reduce the account balance in account A, the way of processing the resource is: "resource consumption ". Similarly, it can be determined that the other three branch transactions deal with resources as: "resource increase", "resource consumption" and "resource increase".

Step 430: Determine a dependency relationship between the plurality of branch transactions according to the processing object and the processing manner.

In an implementation manner, multiple branch transactions may be classified according to a processing manner. After classifying the branch transactions, the dependencies between the branch transactions of different classes are determined according to the processing objects. Specifically, for each of the plurality of branch transactions, it is determined whether the processing manner of the resource corresponding to the processing object by the branch transaction is a resource increase. If yes, it is determined that the category of the branch transaction is a resource addition class. If not, it is determined that the category of the branch transaction is a resource consumption class. For a branch transaction that adds a class to a resource, you can directly determine the branch transaction of the class as a branch transaction that does not have a dependency. For the branch transaction of the resource consumption class, it is determined whether the processing object of the branch transaction of the resource consumption class is the same as the processing object of the branch transaction of the resource addition class. If yes, it is determined that the branch transaction of the resource consumption class is a branch transaction with a dependency. If not, it is determined that the branch transaction of the resource consumption class is a branch transaction that does not have a dependency.

As in the previous example, the processing of the resource corresponding to the processing object is handled by the second branch transaction (corresponding to the branch transaction of "B+100") and the fourth branch transaction (the branch transaction corresponding to "C+5"). As the "resource increase", it can be determined that the category of the two branch transactions is a resource addition class. Since the first branch transaction (corresponding to the branch transaction of "A-100") and the third branch transaction (corresponding to the branch transaction of "B-5"), the processing of the resource corresponding to the processing object is "resource consumption". ", so you can determine the category of the two branch transactions as a resource consumption class.

For two branch transactions of the resource increase class, it can be determined that the two branch transactions are branch transactions that do not have a dependency. For the two branch transactions of the resource consumption class, since the third branch transaction is the same as the processing object (account B) of the second branch transaction, it can be determined that the third branch transaction is a branch transaction with a dependency. The first branch transaction is different from the processing object of the two branch transactions of the resource addition class, so the first branch transaction is determined to be a branch transaction without a dependency.

Step 440, processing multiple branch transactions in parallel and/or serially according to the dependency.

In one implementation, a branch transaction without a dependency may be divided into a first packet, and a branch transaction with a dependency may be divided into a second group. The branch transactions in the first packet are processed in parallel. After the branch transaction in the first packet ends, the branch transaction in the second packet is processed in parallel.

As in the previous example, the second branch transaction, the fourth branch transaction, and the first branch transaction may be divided into the first packet. The third branch transaction is divided into second packets. After that, the second branch transaction, the fourth branch transaction, and the first branch transaction are processed in parallel. After the three branch transactions are completed, the third branch transaction is processed. Here, it can also be understood that the third branch transaction is serially processed.

The distributed transaction processing method provided by the foregoing embodiment of the present specification can improve the processing efficiency of the distributed transaction and ensure the correctness of the processing. As in the foregoing example, the branch transactions corresponding to "A-100", "B+100", and "C+5" are processed in parallel first, and then in the case where the serial processing corresponds to the "B-5" branch transaction, Avoid when the account corresponding to the "B-5" branch is processed first, if the account balance of account B is 0, the failure will be dealt with. That is to say, in the embodiment of the present specification, when the processing objects of the branch transactions are the same, the correctness of the processing can be ensured by setting the processing order.

It can be understood that in the transaction processing method provided by the above embodiment of the present specification, it is assumed that the transaction manager calls the service (or participant) time T, and it is assumed that the distributed transaction is divided into N branch transactions. Then, in the case where there is no dependency between N branch transactions, the processing time overhead of the distributed transaction is T. In the case of a dependency between N branch transactions, the processing time overhead of the distributed transaction is 2T. Therefore, it can be seen that in the case that there is no dependency relationship in the distributed transaction, the solution provided by the present specification can control the distributed transaction processing time within the single-branch transaction processing time range, and does not cause the whole because of the increase of the participants. Distributed transaction processing time increases. Even if there is a dependency between the branches, the processing time is still controllable, and the processing time does not increase as the size of the participants increases.

Corresponding to the above-mentioned distributed transaction processing method, an embodiment of the present specification further provides a distributed transaction processing apparatus. As shown in FIG. 5, the apparatus includes:

The obtaining unit 501 is configured to acquire multiple branch transactions corresponding to the distributed transaction.

The parsing unit 502 is configured to parse the plurality of branch transactions acquired by the obtaining unit 501 to determine a processing object of each of the plurality of branch transactions and a processing manner of the resource corresponding to the processing object.

Here, the processing object may be a user's account or the like. The resource corresponding to the processing object may be an account balance or the like.

The determining unit 503 is configured to determine a dependency relationship between the plurality of branch transactions according to the processing object and the processing manner parsed by the parsing unit 502.

Optionally, the determining unit 503 is specifically configured to: classify the plurality of branch transactions according to the processing manner; and determine, according to the processing object, the dependencies between the branch transactions of different categories.

Optionally, the determining unit 503 is further specifically configured to:

For each of the plurality of branch transactions, it is determined whether the processing method of the resource corresponding to the processing object by the branch transaction is a resource increase.

If so, it is determined that the category of the branch transaction is a resource addition class.

If not, it is determined that the category of the branch transaction is a resource consumption class.

The branch transaction of the resource addition class is determined to be a branch transaction without a dependency.

For the branch transaction of the resource consumption class, it is determined whether the processing object of the branch transaction of the resource consumption class is the same as the processing object of the branch transaction of the resource addition class.

If so, it is determined that the branch transaction of the resource consumption class is a branch transaction with a dependency.

If not, it is determined that the branch transaction of the resource consumption class is a branch transaction without a dependency.

The processing unit 504 is configured to process multiple branch transactions in parallel and/or serial according to the dependencies determined by the determining unit 503.

Optionally, the processing unit 504 is specifically configured to:

Branch transactions that do not have dependencies are divided into first packets, and branch transactions that have dependencies are divided into a second group.

The branch transactions in the first packet are processed in parallel.

After the branch transaction in the first packet ends, the branch transaction in the second packet is processed in parallel.

The functions of the functional modules of the apparatus in the foregoing embodiments of the present invention can be implemented by the steps of the foregoing method embodiments. Therefore, the specific working process of the apparatus provided in one embodiment of the present specification is not described herein.

In the distributed transaction processing apparatus provided by an embodiment of the present specification, the obtaining unit 501 acquires a plurality of branch transactions corresponding to the distributed transaction. The parsing unit 502 parses the plurality of branch transactions to determine a processing target of each of the plurality of branch transactions and a processing manner of the resource corresponding to the processing object. The determining unit 503 determines the dependency relationship between the plurality of branch transactions according to the processing object and the processing manner. Processing unit 504 processes multiple branch transactions in parallel and/or serially depending on the dependencies. Thereby, the processing efficiency of the distributed transaction can be improved.

Those skilled in the art will appreciate that in one or more examples described above, the functions described in this specification can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.

The specific embodiments of the present invention have been described in detail with reference to the specific embodiments of the present invention. The scope of protection, any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of this specification are included in the scope of protection of this specification.

Claims (10)

A distributed transaction processing method, comprising: The transaction manager obtains multiple branch transactions corresponding to the distributed transaction; Parsing the plurality of branch transactions to determine respective processing objects of the plurality of branch transactions and processing manners of resources corresponding to the processing objects; Determining a dependency relationship between the plurality of branch transactions according to the processing object and the processing manner; The plurality of branch transactions are processed in parallel and/or serially according to the dependency. The method according to claim 1, wherein the determining the dependency relationship between the plurality of branch transactions according to the processing object and the processing manner comprises: Classifying the plurality of branch transactions according to the processing manner; According to the processing object, a dependency relationship between branch transactions of different categories is determined. The method of claim 2 wherein: And classifying the plurality of branch transactions according to the processing manner, including: Determining, by each branch transaction of the plurality of branch transactions, whether the processing manner of the resource corresponding to the processing object by the branch transaction is a resource increase; If yes, determining that the category of the branch transaction is a resource addition class; If not, determining that the category of the branch transaction is a resource consumption class; Determining, according to the processing object, a dependency relationship between branch transactions of different categories, including: Determining a branch transaction of a resource addition class as a branch transaction without a dependency; Determining, by the branch transaction of the resource consumption class, whether the processing object of the branch transaction of the resource consumption class is the same as the processing object of the branch transaction of the resource addition class; If yes, determining that the branch transaction of the resource consumption class is a branch transaction with a dependency relationship; If not, it is determined that the branch transaction of the resource consumption class is a branch transaction without a dependency. The method according to claim 3, wherein said processing said plurality of branch transactions in parallel and/or serially according to said dependency relationship comprises: Dividing the branch transaction without the dependency into a first group, and dividing the branch transaction with the dependent relationship into a second group; Processing branch transactions in the first packet in parallel; After the branch transaction in the first packet ends, the branch transaction in the second packet is processed in parallel. The method according to any one of claims 1 to 4, wherein the processing object is an account of a user, and the resource corresponding to the processing object is an account balance. A distributed transaction processing device, comprising: An obtaining unit, configured to acquire multiple branch transactions corresponding to the distributed transaction; a parsing unit, configured to parse the plurality of branch transactions acquired by the acquiring unit to determine a processing object of each of the plurality of branch transactions and a processing manner of resources corresponding to the processing object; a determining unit, configured to determine a dependency relationship between the plurality of branch transactions according to the processing object parsed by the parsing unit and the processing manner; And a processing unit, configured to process the plurality of branch transactions in parallel and/or serial according to the dependency determined by the determining unit. The device according to claim 6, wherein the determining unit is specifically configured to: Classifying the plurality of branch transactions according to the processing manner; According to the processing object, a dependency relationship between branch transactions of different categories is determined. The device according to claim 7, wherein the determining unit is further configured to: Determining, by each branch transaction of the plurality of branch transactions, whether the processing manner of the resource corresponding to the processing object by the branch transaction is a resource increase; If yes, determining that the category of the branch transaction is a resource addition class; If not, determining that the category of the branch transaction is a resource consumption class; Determining a branch transaction of a resource addition class as a branch transaction without a dependency; Determining, by the branch transaction of the resource consumption class, whether the processing object of the branch transaction of the resource consumption class is the same as the processing object of the branch transaction of the resource addition class; If yes, determining that the branch transaction of the resource consumption class is a branch transaction with a dependency relationship; If not, it is determined that the branch transaction of the resource consumption class is a branch transaction without a dependency. The device according to claim 8, wherein the processing unit is specifically configured to: Dividing the branch transaction without the dependency into a first group, and dividing the branch transaction with the dependent relationship into a second group; Processing branch transactions in the first packet in parallel; After the branch transaction in the first packet ends, the branch transaction in the second packet is processed in parallel. The device according to any one of claims 6-9, wherein the processing object is an account of a user, and the resource corresponding to the processing object is an account balance.

Images