7 results about "Lock manager" patented technology

The application discloses a kind of distributed reservation systems and methods for multi-resource cooperation, comprising: transaction manager, at least two resource managers, lock manager, transaction log module and workflow controller;Transaction manager coordinates each resource manager through two-phase commit 2PC protocol, realizes the atomicity execution of cross-node shadow and summary table update;Lock manager adopts read-write lock separation mechanism to resolve concurrent conflict, and handles deadlock problem through timeout detection and active unlocking strategy;Transaction log module is based on prewrite log mechanism Complete record shadow and summary table linkage operation details, provide reliable support for fault recovery and transaction rollback;Workflow controller encapsulates distributed call details, realizes service survival real-time detection and automatic reconnection function.The application has high expansibility, strong consistency, high concurrent adaptation capability and perfect exception fault-tolerant mechanism, and can be widely applied to travel service scene of multi-node deployment.

A relational database system is disclosed that supports operation with versioned metadata. The relational database system includes a lock manager, a transaction manager, and a version-aware metadata storage and cache configured to store and manage versions of metadata to determine which of such versions should be visible at any given point in time, and support to create a correct version of metadata. In one aspect, a transaction manager manages a transaction identifier and its associated start time, end time, and / or commit time. Such data supports the determination of transaction visibility at any point in time, thus supporting the determination of metadata version visibility. In one aspect, such metadata versioning supports snapshot isolation enabling metadata transactions.

The invention relates to the technical field of data storage management, and provides an execution processing system of a backup set, a backup set use end and a lock manager. The system comprises a backup set using end and a lock manager, the backup set use end is used for determining a lock type applied by an operation type according to the job type and the operation type for the target backup set; the backup set use end is further used for generating a job request of a target backup set according to the lock type and the operation type and sending the job request to the lock manager; the lock manager is used for determining a lock type and an operation type according to the job request, determining a lock response result according to conflict detection logic of various preset operation requests, and feeding back the lock response result to the backup set use end; and the backup set use end is used for executing processing on the target backup set according to the lock response result. By adopting the system, the job operation efficiency can be improved, and conflicts caused by multi-job concurrent operation sharing metadata can be coordinated.

A system can maintain a filesystem across nodes of a cluster. The system can, based on receiving a first request from a first node to ingest or write data to a location on a second node, issue, by a lock manager, a write lock on the location of the second node. The system can, based on the first node receiving the write lock, write, by the first node, the data to a write back cache of the first node while refraining from writing the data to the location on the second node. The system can, before the first node flushes the write back cache, comprising writing the data to the location of the second node, respond, by the lock manager, to a second request to read the location on the second node with a read lock that indicates reading the data in the write back cache on the first node.

The application discloses a transaction processing method and device, computer equipment and a storage medium, and belongs to the technical field of databases. The method comprises the following steps: determining a latest transaction for modifying a data record operated by a target transaction based on the data record; performing conflict detection on lock application of the target transaction based on global read lock information and write lock waiting information of the latest transaction; and applying for adding a lock corresponding to an operation type of the operation to the data record in the case where the conflict detection indicates that there is a conflict. The application implements concurrent control through a transaction lock scheme, does not need to depend on a global lock manager, only applies to create lock information in the case where there is a conflict, does not need to consume resources to maintain lock information in the case where there is no conflict, can greatly reduce the creation of unnecessary row locks in the system, and thus saves storage overhead and memory occupation of concurrent control under the lock mechanism.

Relational database systems are disclosed that are enabled to operate with versioned metadata. The relational database system includes a lock manager, a transaction manager and a version aware metadata storage and cache configured to store to store and manage versions of metadata, to determine which of such versions should be visible at any given point in time, and to enable creation of the proper versions of metadata. In an aspect, the transaction manager manages transaction identifiers and their associated start times, abort times and / or commit times. Such data enables determination of transaction visibility, and consequently the metadata version visibility, for any point in time. In an aspect, such metadata versioning support enables snapshot isolation of metadata transactions.