13 results about "Commit Operation" patented technology

The embodiment of the invention provides a log processing method, computing equipment, a storage medium and a program product. The method comprises the following steps: under the condition that a target transaction of a database is detected to meet a target condition, storing a temporary file generated by the target transaction to a storage node; the temporary file stores a binary log for the database; and in response to a transaction submission operation of the target transaction, processing the temporary file in the storage node to generate a binary log file. According to the technical scheme provided by the embodiment of the invention, the transaction submission efficiency is improved.

A lead-sync log record is used to synchronize the replication logs of follower shards to the leader shard. In response to a failure to determine that there is a consensus for a database transaction commit operation after a shard server becomes a new leader, the new leader shard performs a sync operation using the lead-sync log record to synchronize replication logs of the follower shards to the replication log of the new leader. A shard server identifies a first transaction having a first log record but not a post-commit log record in the replication log, defines a recovery window in the replication log starting at the first log record of the identified first transaction and ending at the lead-sync log record, identifies a set of transactions to be recovered, and performs a recovery action on the set of transactions to be recovered.

Provided in the embodiments of the present application are a log processing method, a computing device, a storage medium and a program product. The method comprises: when it is detected that a target transaction of a database meets a target condition, storing in a storage node a temporary file generated by the target transaction, wherein the temporary file saves a binlog for the database; and in response to a transaction committing operation for the target transaction, processing the temporary file in the storage node to generate a binlog file. The technical solution provided in the embodiments of the present application improves the efficiency of transaction committing.

A method, system, and computer program product configured to perform operations including: detecting, using a first thread associated with a first change data capture (CDC) replication mode, that a database transaction associated with a source database exceeds a threshold time value; based on the detecting, spawning a second thread that is configured to identify log entries associated with the database transaction; confirming the database transaction qualifies as a long transaction based on a commit operation in the log entries associated with the database transaction; based on the confirming, switching to a second replication mode for a table associated with the database transaction; updating the table in a target database using values obtained by executing queries on the source database; and based on the updating the table in the target database, terminating the second thread and switching back to the first CDC replication mode for the table.

The application discloses a code submission method and device, electronic equipment and computer program product, and relates to the technical field of computers.The method comprises the following steps: in response to a code submission operation of a first branch, a first audit request is sent to a code audit system; a modification difference file of a first audit identifier is obtained according to the first audit identifier generated by the code audit system based on the first audit request; after the audit result of the first audit identifier returned by the code audit system is passed, code modification description information of the first audit identifier is obtained; and based on the code modification description information, the first audit identifier and branch information of the first branch, submission information of the first branch is generated; and at least one of the modification difference file and a target code file and the submission information of the first branch are submitted to the first branch in a code repository.The application solves the technical problem that redundant manual operation exists when a code file is submitted in the related art, resulting in low submission efficiency.

This invention relates to the field of middleware technology and provides an XA-based transaction coordination method and apparatus, comprising: registering branch transactions when the global transaction manager declares the start of a global transaction; wherein the branch transactions include: a Java branch transaction and a C language branch transaction; invoking a first business program of the Java branch transaction through a client, and operating a first database through the first business program via JDBC; requesting the C language branch transaction to have the transaction middleware invoke a client business program, and operating a second database through the client business program; receiving the execution information of the branch transaction through the client, determining the return result, and returning it to the client; wherein the return result includes a commit operation or a rollback operation.

The invention discloses a distributed transaction processing method, system and device and a storage medium, and the method comprises the steps: receiving a distributed transaction request, analyzing the business semantic features of the distributed transaction request, and creating a distributed transaction list containing the features, and the list comprises a plurality of execution commands carrying the business semantic features; and sending an instruction to each transaction server based on the list to execute the local transaction, and collecting an execution result. And when all the local transactions are successfully executed, sending a pre-submission request to all the servers and collecting a feedback result. Executing a transaction submission or compensation operation according to the pre-submission feedback result, wherein the submission operation comprises issuing a submission instruction to each server; and the compensation operation dynamically matches a target compensation strategy from a compensation strategy library based on the business semantic features, and automatically generates and executes a compensation voucher according to the target compensation strategy. According to the method, intelligent processing of distributed transactions is improved through business semantic perception and an automatic compensation mechanism, so that the efficiency of transaction processing is effectively improved.

The present invention relates to a fault recovery method, device, and system for setting transaction operation dependencies. The method portion mainly includes: after the target-side data synchronization service receives the operation of the source side, it determines whether the difference between the LSN of the current operation and the LSN value of the last checkpoint is greater than or equal to a preset value N. If so, the operations within the range of the last checkpoint LSN to the current LSN 1 are classified as transactions and saved in a checkpoint file; after the target-side data synchronization service receives the commit operation of the transaction, it asynchronously executes and stores the transaction; when the system restarts after the failure, the last checkpoint file is used to restore the KEY in the hash table R. The present invention can achieve seamless connection between the operations received after the failure and the conflict detection of the operations before the failure, thereby ensuring that the failure will not affect the parallel execution capability of transactions before and after the failure.

The application relates to a parallel execution method, device and system based on transaction operation dependency relationship. The method mainly comprises the following steps: a work thread extracts an operation of a transaction, judges whether the current operation is a commit operation, if yes, the current transaction is committed, and the work thread waiting for the current operation is woken up; if not, a conflict TRXID and a conflict LSN saved in the operation are obtained, conflict detection of the operation is carried out, the conflict TRXID of the current operation to be executed is used to search whether there is a transaction with the conflict TRXID in a hash table P, if yes, the work thread waits for itself to be woken up; if not, the work thread uses the operation table information of the current operation to be executed to search whether there is a transaction with the same operation table in a hash table G, and the transaction has a commit LSN smaller than that of the current transaction, and a start LSN of the transaction is smaller than the conflict LSN of the current operation, if yes, the work thread waits for itself to be woken up; if not, the current operation is executed. The application can effectively increase the concurrency of operation execution, and the synchronization performance is improved.

A transaction pattern table is maintained using a transaction stream monitor that monitors a transaction stream. Transactions are completed within a transaction processing system, and transactions are replicated from a source database to a target database by a replication engine. The transaction pattern table includes a plurality of records. Each record includes a transaction pattern. Each completed transaction is a series of one or more transaction steps or operations, and the transaction pattern is a series of one or more transaction steps or operations of the completed transaction. In operation, each transaction step or operation is analyzed in the transaction stream by the transaction stream monitor. It is then detected as to whether a transaction step or operation begins a new transaction. Monitoring of the transaction stream continues for transaction steps or operations for the detected new transaction and the transaction steps or operations for the transaction for the detected new transaction are entered into a change pattern. A first action is taken with respect to the change pattern for the transaction for the detected new transaction when a transaction step or operation for the detected new transaction is an abort or rollback operation, and a second action is taken with respect to the change pattern for the transaction for the detected new transaction when a transaction step or operation for the detected new transaction is a commit operation.

The invention provides a Java system preheating method and device based on a simulation message. The method comprises the following steps: acquiring a preset configuration file of a Java application; under the condition that the Java application automatically enters a preheating mode after being started, a database layer of the Java application is set to be in an automatic rollback mode, and the automatic rollback mode is a mode that a transaction manager does not carry out submission operation and carries out rollback operation at the end position of a transaction; calling the corresponding simulation transaction message for preheating according to the optimal transaction calling times corresponding to each simulation transaction message in the configuration file until all simulation transaction messages are called; and setting the database layer to be in a normal submission mode, and prompting that the Java application is successfully started. The problem that in the prior art, preheating can only be achieved by depending on the application node access cluster and depending on the gray release capacity of a distributed system, and consequently manpower and physical resource cost is too high is solved.

The application discloses a code pre-commit verification method and device, equipment and a storage medium. When a code commit operation performed by a developer is detected, a pre-constructed hook script is activated to verify and intercept the code commit operation, and context information corresponding to the code commit operation is triggered. The changed file is determined from the context information. The change type of the changed file is analyzed, and the build range is determined according to the change type. The build range is incrementally built to determine the compilation result. If the compilation result is a compilation failure, the code commit operation is blocked. If the compilation result is successful, the code commit operation is continued. The application determines the changed file to build according to the actual influence range, solves the efficiency problem of long time consumption of full build, and then determines whether to commit according to the success or failure of the compilation result.

The application discloses a blockchain transaction management method, device and equipment and a storage medium. The application obtains transaction information of a to-be-transacted block, performs a consensus judgment operation on the to-be-transacted block, determines that the to-be-transacted block is a correct block, translates the transaction information into a first sql statement and a second sql statement, executes the first sql statement and the second sql statement, obtains an execution result, queries whether the execution result contains a negative value, if the execution result contains the negative value, restores an asset data table to data before a set of executed sql statements, if the execution result does not contain the negative value, writes to-be-transacted block data after a transaction into a block data table of a relational database, and executes a commit operation to complete the transaction. The application translates the obtained transaction information into sql statements, executes the sql statements in the asset data table of the relational database, and obtains an execution result of the transaction. Compared with the prior art of reading asset data one by one, the application improves data reading efficiency through the relational asset data table, and further improves the efficiency of high-frequency transactions.