CN109783204A - Distributed transaction processing method, device and storage medium - Google Patents

Abstract

Embodiments of the present invention provide a distributed transaction processing method and apparatus, wherein the method is applied to a coordination device, and the coordination device is used to manage at least one execution device, and the method includes: receiving a data from the at least one execution device. A transaction participation request from the first execution device; the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions; receive a transaction submission request sent by the first execution device; The transaction commit request is used to represent that the first execution device has completed the local transaction; based on the transaction commit request of the first execution device, a transaction commit instruction is sent to the first execution device.

Description

Distributed transaction processing method, device and storage medium

technical field

The invention relates to a background distributed system, in particular to a distributed transaction processing method, device and storage medium.

Background technique

In a distributed system, in order to ensure high availability of data, multiple copies of data are usually kept, and these copies are placed on different physical machines. In the case of multiple copies of data, if the network, server or software fails, some copies will be successfully written and some copies will fail. This results in data inconsistency among the replicas, conflicts in data content, and actual data inconsistency.

In order to solve this distributed consistency problem, the Two-Phase Commit Protocol (2PC) shown in Figure 1 and the Three-Phase Commit Protocol (3PC) shown in Figure 2 have been proposed ), but both commit protocols have their own flaws. The two-phase commit protocol has problems such as synchronization blocking and single point of failure; while the three-phase commit protocol has the problem of data inconsistency.

SUMMARY OF THE INVENTION

In view of this, the main purpose of the present invention is to provide a distributed transaction processing method, device and storage medium, which can solve the problem of transaction blocking in a distributed system and ensure data consistency.

In order to achieve the above object, the technical scheme of the present invention is achieved in this way:

A distributed transaction processing method according to an embodiment of the present invention is applied to a coordination device, and the coordination device is used to manage at least one execution device, wherein the method includes:

receiving a transaction participation request from a first execution device in the at least one execution device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions;

receiving a transaction submission request sent by the first execution device; wherein the transaction submission request is used to indicate that the first execution device has completed the local transaction;

Based on the transaction commit request of the first execution device, a transaction commit instruction is sent to the first execution device.

In the above solution, before the transaction commit instruction is sent to the first execution device, the method further includes:

After it is determined that the transaction commit request sent by the first execution device is received, log and lock information related to the local transaction executed by the first execution device is stored in a database table.

In the above scheme, the method further includes:

Detecting whether a transaction commit confirmation message sent by all execution devices in the at least one execution device is received;

If so, confirm that the global transaction is completed; based on the identifier of the global transaction, clean up the database corresponding to the at least one execution device; wherein, the global transaction is composed of local transactions executed by the execution devices managed by the coordination device .

An embodiment of the present invention further provides a distributed transaction processing method, which is applied to the first execution device, wherein the method includes:

Send a transaction participation request to the coordination device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions; the coordination device is used to manage at least one execution device, and the The at least one execution device includes a first execution device;

Execute a local transaction, and send a transaction submission request to the coordination device when the processing of the local transaction is completed; wherein, the local transaction is the first execution device allocated by the coordination device before receiving the transaction participation request. transaction; wherein, the transaction commit request is used to represent that the first execution device has completed the local transaction;

When receiving the transaction commit instruction sent by the coordinating device, commit the local transaction.

In the above solution, after the local transaction is submitted, the method further includes:

An acknowledgment message is sent to the coordinating device, the acknowledgment message being used to notify that the local transaction has been committed.

In the above solution, after the local transaction is submitted, the method further includes:

Release the connection resources of the database participating in the local transaction.

The present invention further provides a distributed transaction processing device, the device includes: a first receiving module, a second receiving module and a first sending module, wherein,

The first receiving module is configured to receive a transaction participation request from a first execution device in the at least one execution device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is in a capable state. the status of executing local transactions;

The second receiving module is configured to receive a transaction submission request sent by the first execution device; wherein the transaction submission request is used to indicate that the first execution device has completed the local transaction;

The first sending module is configured to send a transaction submission instruction to the first execution device based on the transaction submission request of the first execution device.

The present invention also provides a distributed transaction processing device, the device includes: a request module, an execution module and a submission module, wherein,

The request module is configured to send a transaction participation request to the coordination device; wherein, the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions; the coordination device is used for Manage at least one execution device, the at least one execution device includes a first execution device;

The execution module is configured to execute a local transaction, and send a transaction submission request to the coordination device when the processing of the local transaction is completed; wherein, the local transaction is a transaction submitted by the coordination device before receiving the transaction participation request. The transaction allocated by the first execution device; wherein, the transaction submission request is used to represent that the first execution device has completed the local transaction;

The committing module is configured to commit the local transaction when receiving the transaction commit instruction sent by the coordinating device.

The present invention also provides a computer-readable storage medium on which a computer program is stored, wherein when the computer program is executed by a processor, any step of the above-mentioned method is executed.

The present invention also provides a distributed transaction processing device, comprising: a processor and a memory for storing a computer program that can be executed on the processor, wherein the processor is configured to execute the above-mentioned computer program when running the computer program. any step of the method.

In the distributed transaction processing method and device provided by the embodiments of the present invention, each executing device submits a participation request to the coordinating device in parallel and executes local tasks independently, without synchronously waiting for other executing devices to confirm whether they can participate in the transaction. , which improves the efficiency of distributed transaction execution; after each execution device completes the local transaction, the coordinating device performs unified management and control to perform commit or rollback, which solves the blocking problem in distributed transactions. Moreover, since the distributed transaction processing method provided by the embodiment of the present invention adopts the methods of local transaction submission and global transaction identifier cleaning in global transaction submission, the data consistency of distributed transactions can be improved, and the maximum performance of distributed transactions can be achieved.

Description of drawings

Fig. 1 is the information interaction diagram of the distributed transaction processing method of the two-phase commit protocol;

Fig. 2 is the information interaction diagram of the distributed transaction processing method of the three-phase commit protocol;

3 is an application scenario of an embodiment of the present invention;

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

5 is a flowchart of another distributed transaction processing method provided by an embodiment of the present invention;

6 is a schematic diagram of interaction between a coordination device and an execution device provided by an embodiment of the present invention;

FIG. 7 is a schematic structural diagram 1 of a distributed transaction processing apparatus provided by an embodiment of the present invention;

FIG. 8 is a second schematic structural diagram of a distributed transaction processing apparatus provided by an embodiment of the present invention;

FIG. 9 is a schematic diagram of a hardware structure of a distributed transaction processing apparatus according to an embodiment of the present invention.

Detailed ways

To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the specific technical solutions of the invention will be described in further detail below with reference to the accompanying drawings in the embodiments of the present invention. The following examples are intended to illustrate the present invention, but not to limit the scope of the present invention.

Before describing the embodiments of the present invention, let's take a detailed look at the relevant background of distributed transactions.

Distributed transaction means that a large operation consists of different small operations. These small operations are distributed on different servers and belong to different applications. Distributed transactions need to ensure that these small operations either all succeed or all fail. Essentially, distributed transactions are to ensure data consistency across different databases. However, different small operations are performed by different nodes, and the independent nodes cannot accurately know the transaction execution status of other nodes. In order to guarantee data consistency in a distributed system, the key to distributed transaction processing is that there must be a way to know all the actions a transaction has made anywhere, and the decision to commit or roll back a transaction must yield a uniform result (all commit or roll back all). Therefore, the conventional solution is to introduce a "coordinator" component to uniformly schedule the execution of all distributed nodes.

In the application scenario shown in Figure 3, when the task comes, the application system (AP, Application), that is, the business system, can divide the business into multiple branch transactions according to the specific situation of the business, and send the divided multiple branch transactions. To the transaction manager (TM, Transaction Manager), that is, the coordination device. Here, the business system AP sends the divided multiple branch transactions to the coordination device TM, which is specifically implemented by invoking the operation interface TX of the distributed transaction.

After receiving the above-mentioned multiple branch transactions, the coordination device TM parses the multiple branches, determines the processing objects and corresponding resources of each branch, and assigns an identifier to the transaction; after determining each branch service, the resource manager ( RM, Resource Manager) provides an operation interface XA to uniformly schedule each resource manager RM, that is, an execution device, to realize distributed transactions. Here, the resource manager RM is generally a database, and may also be other resource managers, such as a message queue (eg, a JMS data source).

It should be noted that in Figure 3, resource control is performed between the business system AP and the execution device RM through the native API (Native API) provided by the RM; here, the local interface does not have an interface specification agreement, and currently each manufacturer owns Implement your own resource control.

There are currently two-phase commit protocols and three-phase commit protocols for implementing distributed transactions through the XA interface specification. In practice, it is found that there are problems such as synchronous blocking, single point of failure and data inconsistency in the two-phase submission, while the three-phase submission solves the single point of failure problem and can reduce blocking, but due to its interaction mechanism, once the participant cannot receive the incoming data in time After the information of the coordinator, it will perform commit by default instead of holding transaction resources and blocking; on the one hand, this mechanism can greatly reduce blocking problems, but it will also cause data consistency problems : Due to network reasons, the abort response sent by the coordinating device TM is not received by the executing device RM in time, then the executing device RM performs a commit operation after waiting for a timeout. In this way, there is data inconsistency between other execution devices RM that receive an abort command and perform rollback.

Based on this, an embodiment of the present invention provides a distributed transaction processing method, which is applied to a coordination device, where the coordination device is used to manage at least one execution device. As shown in FIG. 4 , the method includes:

S101, receiving a transaction participation request of a first execution device in the at least one execution device; wherein, the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions;

S102, receiving a transaction submission request sent by the first execution device; wherein the transaction submission request is used to indicate that the first execution device has completed the local transaction;

S103, based on the transaction commit request of the first execution device, send a transaction commit instruction to the first execution device.

Here, the coordination device TM is a device used to uniformly schedule all distributed nodes in a distributed system, that is, a device that performs tasks performed by the device RM. The executor of a business is the coordinating device TM, and it can also be based on the interrelated relationship between the various sub-services in the business, and the executing device with the most association relationship is selected as the coordinating device TM. Of course, the determination of the coordinating device TM here can also be is another way of determining.

The execution device RM is a device that executes local transactions in a distributed system. In a distributed system, there is generally only one coordinating device TM, but there are multiple executing devices RM. The "first", "second", etc. are only used for distinguishing descriptions, and should not be construed as indicating or implying relative importance.

In step S101, the coordination device TM receives the transaction participation request of the first execution device in the at least one execution device, which specifically includes: when the service comes, the service system AP divides the service into multiple branch transactions according to the specific situation of the service , and send the divided multiple branch transactions to the coordination device TM, and the coordination device TM registers the execution device RM through the XA interface according to the situation of each branch transaction, that is, registers the execution device RM required by this service. Here, when some of the registered execution devices RM are in a state capable of executing local transactions, the execution devices RM in the state capable of executing local transactions take the initiative to send a transaction participation request to the coordinating device TM, and the coordinating device TM receives the Transaction participation request of the first execution device.

In step S102, the coordination device TM receives a transaction commit request sent by the first execution device; here, the transaction commit request is used to indicate that the first execution device has completed the local transaction;

In step S103, after the coordination device TM receives the transaction submission request, the coordination device TM sends a transaction submission instruction to the first execution device based on the transaction submission request of the first execution device to start a formal submission process.

Here, before the coordination device TM sends a transaction commit instruction to the first execution device, the distributed transaction processing method further includes:

After it is determined that the transaction commit request sent by the first execution device is received, log and lock information related to the local transaction executed by the first execution device is stored in a database table.

Here, the coordination device TM receives the transaction submission request sent by the first execution device, and stores the log information and lock information about the local task performed by the first execution device.

It should be noted that the log information includes the undo log and the redo log of the local transaction; the lock information refers to locking resources before committing the transaction. The undo log is used to store the value before data modification; the redo log is used to record the modified data, which is recorded sequentially.

It should also be noted that, generally, a relational database management system is composed of two files, a database file and a log file. When the database performs any write operation, it must first write the log; when executing a transaction, the database first records the local redo log of the transaction, that is, records the modified data, and then starts to actually operate the database; The log file is written to disk first. Then, when there is a sudden power failure, even if the operation is not completed, when the database is restarted, the database will perform undo rollback or redo rollforward according to the current data situation, which ensures strong data consistency.

When the database modifies the data, it needs to read the data pages from the disk into the cache area (BufferPool). After the data page is read from the disk to the cache area, if the data is modified in the cache area, the content of the data page in the cache area is inconsistent with the data page on the disk. At this time, the data page in the cache area is called a dirty page ( dirty page). If an abnormal database service restart occurs at this time, the data will not be synchronized to the disk file, that is, data loss will occur. If there is a file at this time, when the dirty page in the cache area is changed, the corresponding modification records can be recorded in the redo log file, then when the database service crashes and the database is restored, it can be based on the redo log file. The recorded content is reapplied to the disk file, and the data remains consistent.

Further, the distributed transaction processing method in this embodiment further includes:

Detecting whether a transaction commit confirmation message sent by all execution devices in the at least one execution device is received;

If so, confirm that the global transaction is completed; based on the identifier of the global transaction, clean up the database corresponding to the at least one execution device; wherein, the global transaction is composed of local transactions executed by the execution devices managed by the coordination device ;

Here, it should be noted that when the executing device performs the submission of the local task according to the transaction submission instruction sent by the coordinating device, if the coordinating device successfully executes the submission operation, it returns an acknowledgment (ACK) response to the coordinating device. A confirmation response is used to characterize that the executing device has correctly committed the transaction.

Then, when the coordinating device receives the transaction commit confirmation message sent by all the executing devices, it means that the global transaction is completed. At this time, based on the identifier of the global transaction, the database corresponding to the at least one execution device is cleaned up, and all database resources are released.

Here, since the coordinating device assigns a uniform identifier to each sub-transaction involved in the entire transaction during transaction allocation, after the transaction is committed, the database resources occupied by the global transaction process need to be released so that other transactions can This database can be accessed.

As an example, when user A buys a commodity, both the payment database and commodity information database of user A will be updated. When the submission operation is performed, the database of the operation needs to be locked to prevent "user A from purchasing a commodity" Transactions other than this transaction operate on the above commodity information database. After the entire task of “User A buys a commodity” is submitted, the related databases involved in the transaction, such as the payment database and the commodity information database, are released. Other transactions (for example: "User B purchases a commodity") can access the payment database and commodity information database.

In an optional embodiment of the present invention, after the above step S103, the method may include:

Determine whether there is an execution device that fails to execute the local transaction, and if so, send a rollback instruction to all execution devices related to the global transaction; wherein, the global transaction is composed of the local transaction executed by the execution device managed by the coordination device;

Here, when the coordinating device does not receive a commit request sent by a certain execution device within a preset time, it is considered that the execution of the local transaction of the certain execution device fails. When there is an execution device that fails to execute a local transaction, the coordinating device can send a rollback instruction to all execution devices related to the global transaction; that is, if one execution device fails to execute a local task, all the execution devices perform data rollback operations .

In another optional embodiment of the present invention, after the above step S103, the method may further include:

Determine whether there is a second execution device that fails to execute the local transaction, and if so, send a rollback instruction to the second execution device.

Here, when only the second execution device fails to execute the local transaction, the coordination device only sends a rollback instruction to the second execution device;

It should be noted that the number of times that the coordinating device sends the rollback instruction to the second execution device cannot be too many. When the rollback operation is executed multiple times and has not been successful, the coordinating device sends all execution devices related to the global transaction. Send a rollback command. Here, since many transactions have time limitations during operation, when the number of rollbacks is too large, the efficiency of global transaction submission will be affected.

In order to express the content of this embodiment more clearly, the description is given here in conjunction with the specific application situation, taking the following business requirements as an example:

In the transfer business, account A transfers 1,000 yuan to account B. During the transfer process, both accounts A and B submit a handling fee of 10 yuan to account C. Then this distributed transaction can be divided into 6 branch transactions, namely: "A-1000", "B+1000", "A-10", "B-10", "C+10", "C+10" "; before carrying out the distributed transaction processing in this embodiment, the business system will send the divided six branch transactions to the coordination device TM, and the coordination device TM determines the resource allocation according to the objects and resources of the six branch transactions. The six execution devices RM required for this distributed transaction are registered through the XA interface, and the RM is notified to open the operation of each database.

When some of the six execution devices RM are in a state capable of executing local transactions, for example, the execution device RM that executes the "A-10" operation is in a state capable of executing transactions, at this time, the distributed transaction processing in this embodiment The first step is: the coordinating device TM will receive the transaction participation request of the executing device RM of the "A-10" operation, and after the "A-10" operation is completed, the coordinating device TM will receive "A-10" A transaction commit request sent by the execution device of the operation; at this time, the coordinating device TM will send a transaction commit instruction to the execution device of the "A-10" operation based on the commit request.

Here, the determining of the processing mode and the dependency relationship of the resources may be the order of finding out the existence of the transactions, or the case where the transactions can be processed in parallel. For example when "A-1000" and "A-10" can be processed in parallel.

The distributed transaction processing method provided by the embodiment of the present invention receives the transaction participation request and the transaction submission request of the execution device by the coordination device, judges the successful execution of the local task of the execution device, and then sends the transaction submission instruction to the execution device. After the task is assigned, there is no need to wait for the command of the coordinating device, which greatly improves the efficiency of execution. At the same time, because the coordinating device can modify the rollback authority, the wrong execution device can be actively rolled back to ensure the atomicity of the transaction. sex.

An embodiment of the present invention provides another distributed transaction processing method, which is applied to the first execution device. As shown in FIG. 5 , the method includes:

S201: Send a transaction participation request to a coordination device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions; the coordination device is used to manage at least one execution device , the at least one execution device includes a first execution device;

S202: Execute a local transaction, and send a transaction submission request to the coordinating device when processing the local transaction is completed; wherein, the local transaction is that the coordinating device is the first executing device before receiving the transaction participation request an assigned transaction; wherein the transaction commit request is used to indicate that the first execution device has completed the local transaction;

S203, when receiving the transaction commit instruction sent by the coordinating device, commit the local transaction.

In step S201, when the service comes, the service system AP divides the service into multiple branch transactions according to the specific conditions of the service, and sends the divided multiple branch transactions to the coordination device TM, and the coordination device TM, according to the situation of each branch transaction, Register the execution device RM through the XA interface, that is, register the execution device RM required for this service. Here, when some of the registered execution devices RM are in a state capable of executing local transactions, the execution devices RM in the state capable of executing local transactions take the initiative to send a transaction participation request to the coordination device TM.

Here, the coordination device TM is a device in a distributed system that is used to uniformly schedule all RMs participating in transactions to execute tasks, and the execution device RM is a device that executes local transactions in a distributed system. There are multiple execution devices RM. At least one execution device includes a first execution device;

In step S202, after the first execution device sends a transaction participation request to the coordination device TM, it starts to execute its assigned branch transaction, that is, a local transaction, and after the local transaction is completed, a transaction submission request is initiated to the coordination device TM; here, The transaction commit request is used to represent that the first execution device has completed the local transaction;

Here, when the first execution device executes the local transaction, the method further includes:

Store local log information.

The local log information includes the undo log and the redo log of the local transaction; the undo log is used to store the value before data modification; the redo log is used to record the modified data, which is recorded sequentially.

It should be noted that when the first execution device executes a local transaction, that is, when operating the database, it will first record the local redo log of the transaction, that is, record the modified data, and then start to actually operate the database; before the operation The log file is first written to disk. Then, when there is a sudden power failure, even if the operation is not completed, when the database is restarted, the database will perform undo rollback or redo rollforward according to the current data situation, which ensures strong data consistency.

In step S203, when receiving the transaction commit instruction sent by the coordinating device, commit the local transaction.

After committing the local transaction, the method further includes:

An acknowledgment message is sent to the coordinating device, the acknowledgment message being used to notify that the local transaction has been committed.

Here, when the first execution device successfully executes the submission of the local transaction according to the transaction submission instruction sent by the coordinator device, it will return an acknowledgement (ACK) response to the coordinator device, and the acknowledgment response is used to represent the first execution device. The transaction has been correctly committed.

After the committing the local transaction, the method further includes:

Release the connection resources of the database participating in the local transaction.

Here, since the database resources are locked when the database is operated, other transactions cannot access the database resources. After the local task is submitted, the database resources occupied by the local transaction need to be released so that other transactions can access the database resources. this database.

As an optional embodiment, after the distributed transaction processing method submits the local transaction, the method further includes:

Receive the data rollback command sent by the coordinating device, and execute the data rollback.

Here, specifically, in the case that the local transaction is not successfully executed, the coordination device will send a data rollback instruction, and execute the data rollback according to the received data rollback instruction.

In order to express the content of this embodiment more clearly, the description is given here in conjunction with the specific application situation, taking the following business requirements as an example:

In the transfer business, account A transfers 1,000 yuan to account B. During the transfer process, both accounts A and B submit a handling fee of 10 yuan to account C. Then this distributed transaction can be divided into 6 branch transactions, namely: "A-1000", "B+1000", "A-10", "B-10", "C+10", "C+10" "; before carrying out the distributed transaction processing in this embodiment, the business system will send the divided six branch transactions to the coordination device TM, and the coordination device TM determines the resource allocation according to the objects and resources of the six branch transactions. The six execution devices RM required for this distributed transaction are registered through the XA interface, and the RM is notified to open the operation of each database.

When some of the six execution devices RM are in a state capable of executing local transactions, for example, the execution device RM that executes the "A-10" operation is in a state capable of executing transactions, at this time, the distributed transaction processing in this embodiment The first step is: the execution device RM that executes the "A-10" operation sends a transaction participation request to the coordinating device TM by itself, and executes the local task by itself, that is, executes the "A-10" operation; after completing the "A-10" operation , send a commit request of the "A-10" operation to the coordination device TM; finally, submit the local transaction "A-10" operation according to the transaction commit instruction received from the coordination device.

In the distributed transaction processing method provided by the embodiment of the present invention, each executing device submits a participation request to the coordinating device in parallel, and each executes local tasks independently, without synchronously waiting for all transaction participants to confirm whether they can participate in the transaction. It solves the blocking problem in distributed transactions very well. After the respective local tasks are completed, a task submission request is initiated, and the local transaction is submitted according to the submission instruction, which can realize the rapid release of database resources.

FIG. 6 is a schematic diagram of interaction between a coordination device and an execution device for implementing a distributed transaction processing method according to an embodiment of the present invention. In FIG. 6, the transaction coordinator TM refers to the coordination device TM, which is used in the distributed system. In order to uniformly schedule devices of all execution devices, the transaction participants refer to execution devices RM. In a distributed transaction, there is only one coordination device TM, but there are multiple transaction participants, ie, multiple execution devices RM. The distributed transaction processing method includes:

S301, a first execution device sends a transaction participation request to a coordination device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions; the coordination device is used to manage at least one execution device, the at least one execution device includes a first execution device;

S302, the coordination device receives a transaction participation request from a first execution device in the at least one execution device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is capable of executing local transactions status;

S303, the first execution device executes a local transaction, and sends a transaction submission request to the coordinating device when processing the local transaction is completed; wherein, the local transaction is that the coordinating device is before receiving the transaction participation request The transaction allocated by the first execution device; wherein, the transaction submission request is used to represent that the first execution device has completed the local transaction;

S304, the coordination device receives a transaction commit request sent by the first execution device; wherein, the transaction commit request is used to indicate that the first execution device has completed the local transaction;

S305. Based on the transaction commit request of the first execution device, the coordination device sends a transaction commit instruction to the first execution device.

S306, when the first execution device receives the transaction submission instruction sent by the coordination device, submit the local transaction.

Here, in step S303, when the first execution device executes the local transaction, the local log information will be stored.

Before step S305, after determining that the coordinating device has received the transaction commit request sent by the first executing device, it stores the log and lock information related to the local transaction executed by the first executing device in a database table . The local log information includes the undo log and the redo log of the local transaction; the undo log is used to store the value before data modification; the redo log is used to record the modified data, which is recorded sequentially. Here, the log and lock information related to local transactions are stored so that in the event of an emergency, the database will perform undo rollback or redo rollforward according to the current data situation, which can ensure strong data consistency.

After step S306, the method further includes: the coordinating device determines whether there is an execution device that fails to execute the local transaction, and if so, sends a rollback instruction to all execution devices related to the global transaction;

Here, another implementation method is also included, that is, the coordination device determines whether there is a second execution device that fails to execute the local transaction, and if there is, sends a rollback instruction to the second execution device.

After the first execution device submits the local transaction, the first execution device will send a confirmation message to the coordination device, where the confirmation message is used to notify that the local transaction has been submitted; the coordination device detects whether it receives A transaction commit confirmation message sent by all execution devices in the at least one execution device; if yes, confirm that the global transaction is completed; The database is cleaned up; the first execution device releases the connection resources of the database participating in the local transaction. Wherein, the global transaction is composed of local transactions executed by the execution device managed by the coordination device;

In order to express the content of this embodiment more clearly, the description is given here in conjunction with the specific application situation, taking the following business requirements as an example:

In the transfer business, account A transfers 1,000 yuan to account B. During the transfer process, both accounts A and B submit a handling fee of 10 yuan to account C. Then this distributed transaction can be divided into 6 branch transactions, namely: "A-1000", "B+1000", "A-10", "B-10", "C+10", "C+10" "; before carrying out the distributed transaction processing in this embodiment, the business system will send the divided six branch transactions to the coordination device TM, and the coordination device TM determines the resource allocation according to the objects and resources of the six branch transactions. The six execution devices RM required for this distributed transaction are registered through the XA interface, and the RM is notified to open the operation of each database.

When some of the six execution devices RM are in a state capable of executing local transactions, for example, the execution device RM that executes the "A-10" operation is in a state capable of executing transactions, at this time, the distributed transaction processing in this embodiment The first step is: the execution device RM that executes the "A-10" operation sends a transaction participation request to the coordination device TM by itself, and executes local tasks by itself; the coordination device TM will receive the execution device RM of the "A-10" operation. After the execution device RM completes the "A-10" operation, the coordinating device TM will receive the transaction submission request sent by the execution device of the "A-10" operation, and based on the submission request, coordinate the The equipment TM sends a transaction commit instruction to the execution equipment RM of the "A-10" operation, and the execution equipment RM commits the local transaction "A-10" operation according to the receipt of the transaction commit instruction sent by the coordination equipment TM.

In the distributed transaction processing method provided by the embodiment of the present invention, each executing device submits a participation request to the coordinating device in parallel, and each executes local tasks independently, without synchronously waiting for all transaction participants to confirm whether they can participate in the transaction. It solves the blocking problem in distributed transactions very well. After each execution device completes the execution of the local transaction, the coordinating device TM performs unified management and control to execute commit or rollback; since the coordinating device can modify the rollback authority, it takes the initiative to roll back the wrong execution device to ensure the transaction atomicity. Moreover, since the distributed transaction processing method provided by the embodiment of the present invention is based on the XA model, it can easily support various resource managers such as databases and message queues. In terms of data consistency, since the distributed transaction processing method provided by the embodiment of the present invention divides the global transaction submission into two steps, and adopts the method of local transaction submission and global transaction identifier cleaning, the maximum performance of the distributed transaction can be achieved.

Based on the same technical concept as the foregoing embodiments, an embodiment of the present invention provides a distributed transaction processing apparatus 400. As shown in FIG. 7, the apparatus includes: a first receiving module 401, a second receiving module 402, and a first sending module 403, of which,

The first receiving module 401 is configured to receive a transaction participation request from a first execution device in the at least one execution device; wherein the transaction participation request is used to indicate to the coordination device that the first execution device is in a The state of being able to perform local transactions;

The second receiving module 402 is configured to receive a transaction submission request sent by the first execution device; wherein, the transaction submission request is used to indicate that the first execution device has completed the local transaction;

The first sending module 403 is configured to send a transaction commit instruction to the first execution device based on the transaction commit request of the first execution device.

The first sending module 403 is further configured to store the log and lock information related to the local transaction executed by the first execution device after receiving the transaction submission request sent by the first execution device. in the database table.

Further, the apparatus 400 further includes: a detection module, the detection module is configured to detect whether a transaction commit confirmation message sent by all execution devices in the at least one execution device is received; if so, confirm that the global transaction is completed ; clean up the database corresponding to the at least one execution device based on the identifier of the global transaction; wherein, the global transaction is composed of local transactions executed by the execution device managed by the coordination device.

The apparatus 400 further includes: a first judging module: the first judging module is used to judge whether there is an execution device that fails to execute the local transaction, and if so, send a rollback instruction to all execution devices related to the global transaction;

The apparatus 400 further includes: a second judging module: the second judging module is configured to judge whether there is a second execution device that fails to execute the local transaction, and if so, send a rollback instruction to the second execution device.

It should be noted that, since the principle of solving the problem of the distributed transaction processing apparatus 400 is similar to the aforementioned distributed transaction processing method applied to the coordination device, the specific implementation process and implementation principle of the distributed transaction processing apparatus 400 are both Reference may be made to the foregoing method and implementation process, as well as the description of the implementation principle, and repeated descriptions will not be repeated.

The distributed transaction processing apparatus provided by the embodiment of the present invention judges the successful execution of the local task of the execution device by receiving the transaction participation request and the transaction submission request of the execution device, and then sends a transaction submission instruction to the execution device. After the task is assigned, there is no need to wait for the command of the coordinating device, which greatly improves the efficiency of execution. At the same time, because the coordinating device can modify the rollback authority, the wrong execution device can be actively rolled back to ensure the atomicity of the transaction. sex.

Based on the same technical concept as the foregoing embodiments, an embodiment of the present invention provides another distributed transaction processing apparatus 500. As shown in FIG. 8, the apparatus includes: a request module 501, an execution module 502, and a submission module 503, wherein,

The request module 501 is configured to send a transaction participation request to the coordination device; wherein, the transaction participation request is used to indicate to the coordination device that the first execution device is in a state capable of executing local transactions; For managing at least one execution device, the at least one execution device includes a first execution device;

The execution module 502 is configured to execute a local transaction, and send a transaction submission request to the coordinating device when processing the local transaction is completed; wherein, the local transaction is that the coordinating device is before receiving the transaction participation request. The transaction allocated by the first execution device; wherein, the transaction submission request is used to represent that the first execution device has completed the local transaction;

The committing module 503 is configured to commit the local transaction when receiving the transaction commit instruction sent by the coordinating device.

The execution module 502 is further configured to store local log information.

The apparatus 500 further includes: a second sending module, configured to send a confirmation message to the coordination device, where the confirmation message is used to notify that the local transaction has been committed.

The apparatus 500 further includes: a release module configured to release connection resources of the database participating in the local transaction.

The apparatus 500 further includes: a third receiving module, where the third receiving module is configured to receive a data rollback instruction sent by the coordination device, and perform data rollback.

It should be noted that since the principle of solving the problem of the distributed transaction processing apparatus 500 is similar to the aforementioned distributed transaction processing method applied to the first execution device, the specific implementation process and implementation of the distributed transaction processing apparatus 500 For the principles, reference may be made to the foregoing method and implementation process, as well as the description of the implementation principle, and repeated descriptions will not be repeated.

In the distributed transaction processing apparatus provided by the embodiment of the present invention, each executing device submits a participation request to the coordinating device in parallel, and each executes local tasks independently, without synchronously waiting for all transaction participants to confirm whether they can participate in the transaction. It solves the blocking problem in distributed transactions very well. After the respective local tasks are completed, a task submission request is initiated, and the local transaction is submitted according to the submission instruction, which can realize the rapid release of database resources.

Embodiments of the present invention further provide a computer-readable storage medium on which a computer program is stored, and when the computer program processor is executed by the processor, the steps of the foregoing method embodiments are implemented, and the foregoing storage medium includes: a removable storage device , Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

An embodiment of the present invention further provides a distributed transaction processing apparatus, comprising: a processor and a memory for storing a computer program that can be executed on the processor, wherein the processor is configured to execute the memory when running the computer program The steps of the above-described method embodiments are in memory.

FIG. 9 is a schematic diagram of a hardware structure of a distributed transaction processing apparatus according to an embodiment of the present invention. The distributed transaction processing apparatus 600 includes: at least one processor 601 and a memory 602. Each component in the distributed transaction processing apparatus 600 passes through a bus system 603 is coupled together, and it can be understood that the bus system 603 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 603 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the various buses are labeled as bus system 603 in FIG. 9 .

It will be appreciated that the memory 602 may be either volatile memory or non-volatile memory, and may include both volatile and non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), an erasable programmable read-only memory (EPROM, Erasable Programmable Read-only memory) Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD-ROM, or Compact Disc Read-Only Memory (CD-ROM, Compact Disc Read-Only Memory); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory may be Random Access Memory (RAM), which is used as an external cache memory. By way of example and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM, SynchronousDynamic Random Access Memory), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Link Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Memory) . The memory 602 described in the embodiments of the present invention is intended to include, but not be limited to, these and any other suitable types of memory.

The memory 602 in the embodiment of the present invention is used for storing various types of data to support the operation of the distributed transaction processing apparatus 600 . Examples of these data include: any computer program used to operate on the distributed transaction processing apparatus 600 , such as stored local log information, data rollback instructions, etc. The programs implementing the methods of the embodiments of the present invention may be contained in the memory 602 .

The methods disclosed in the above embodiments of the present invention may be applied to the processor 601 or implemented by the processor 601 . A processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above-mentioned method can be completed by a hardware integrated logic circuit in a processor or an instruction in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The processor may implement or execute the methods, steps, and logical block diagrams disclosed in the embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, the storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps of the foregoing method in combination with its hardware.

In an exemplary embodiment, the distributed transaction processing apparatus 600 may be implemented by one or more Application Specific Integrated Circuit (ASIC, Application Specific Integrated Circuit), DSP, Programmable Logic Device (PLD, Programmable Logic Device), complex programmable logic Device (CPLD, Complex Programmable LogicDevice), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array), General Purpose Processor, Controller, Microcontroller (MCU, Micro Controller Unit), Microprocessor (Microprocessor), or Other electronic components are implemented for performing the above method.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms. of.

The unit described above as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may all be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integration The unit can be implemented either in the form of hardware or in the form of hardware plus software functional units.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by program instructions related to hardware, the aforementioned program can be stored in a computer-readable storage medium, and when the program is executed, execute Including the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: a mobile storage device, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk and other various A medium on which program code can be stored.

Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present invention may be embodied in the form of software products in essence or the parts that make contributions to the prior art. The computer software products are stored in a storage medium and include several instructions for A computer device (which may be a personal computer, a server, or a network device, etc.) is caused to execute all or part of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic disk or an optical disk and other mediums that can store program codes.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be included within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (10)

1. a kind of distributed transaction processing method is applied to coordinate equipment, the coordination equipment is for managing at least one execution Equipment, which is characterized in that the described method includes:

It receives at least one described first affairs for executing equipment executed in equipment and participates in request；Wherein, the affairs participate in It requests for indicating the first execution equipment in the state for being able to carry out local matter to the coordination equipment；

It receives the affairs that the first execution equipment is sent and submits request；Wherein, the affairs submit request described for characterizing The local matter is completed in first execution equipment；

The affairs for executing equipment based on described first submit request, and Xiang Suoshu first executes equipment transmission affairs and submits instruction.

2. the method according to claim 1, wherein described refer to the first execution equipment transmission affairs submission Before order, the method also includes:

After determining that receiving the affairs that described first executes equipment transmission submits request, described first is executed performed by equipment Log relevant to local matter and lock information are stored in database table.

3. the method according to claim 1, wherein the method also includes:

Detect whether that receiving the affairs that at least one described whole execution equipment executed in equipment are sent submits confirmation messages；

If so, confirmation global transaction is completed；Based on the identifier of the global transaction, at least one described execution equipment institute Corresponding database is cleared up；Wherein, the global transaction local thing as performed by the execution equipment of coordination equipment management Business composition.

4. a kind of distributed transaction processing method is applied to first and executes equipment, which is characterized in that the described method includes:

Affairs participation request is sent to equipment is coordinated；Wherein, the affairs participate in request for indicating institute to the coordination equipment It states the first execution equipment and is in the state for being able to carry out local matter；The coordination equipment is set for managing at least one execution It is standby, equipment is executed comprising first at least one described execution equipment；

Local matter is executed, affairs is sent to the coordination equipment when completing the processing of the local matter and submits request；Its In, the local matter is that the coordination equipment is that the first execution equipment is distributed before receiving affairs and participating in request Affairs；Wherein, the affairs submit request that the local matter is completed for characterizing the first execution equipment；

When receiving the affairs submission instruction that the coordination equipment is sent, the local matter is submitted.

5. according to the method described in claim 4, it is characterized in that, the method is also after the submission local matter Include:

Confirmation message is sent to equipment is coordinated, the confirmation message is for notifying the local matter to have been filed on.

6. according to the method described in claim 4, it is characterized in that, the method is also after the submission local matter Include:

Release participates in the connection resource of the database of the local matter.

7. a kind of distributing real time system device, described device includes: the first receiving module, the second receiving module and the first transmission Module, wherein

First receiving module is asked for receiving at least one described affairs participation for executing the first execution equipment in equipment It asks；Wherein, the affairs participate in request and are able to carry out this for being in coordination equipment instruction the first execution equipment The state of ground affairs；

Second receiving module submits request for receiving the affairs that the first execution equipment is sent；Wherein, the affairs Submit request that the local matter is completed for characterizing the first execution equipment；

First sending module, the affairs for executing equipment based on described first submit request, and the execution of Xiang Suoshu first is set Preparation send affairs to submit instruction.

8. a kind of distributing real time system device, described device includes: request module, execution module and submission module, wherein

The request module participates in request for sending affairs to coordination equipment；Wherein, the affairs participate in request for institute It states coordination equipment and indicates that the first execution equipment is in the state for being able to carry out local matter；The coordination equipment is for managing At least one executes equipment, includes the first execution equipment at least one described execution equipment；

The execution module is sent out when completing the processing of the local matter to the coordination equipment for executing local matter Affairs are sent to submit request；Wherein, it is described before receiving affairs and participating in request that the local matter, which is the coordination equipment, First executes the affairs of equipment distribution；Wherein, the affairs submit request that institute is completed for characterizing the first execution equipment State local matter；

The submission module, for submitting the local thing when receiving the affairs submission instruction that the coordination equipment is sent Business.

9. a kind of computer readable storage medium, is stored thereon with computer program, which is characterized in that the computer program quilt The step of any one of claim 1 to 6 the method is realized when processor executes.

10. a kind of distributing real time system device characterized by comprising processor and for store can be on a processor The memory of the computer program of operation, wherein the processor is for when running the computer program, perform claim to be required The step of any one of 1 to 6 the method.