Patent application number | Description | Published |
20130019000 | MULTI-OPERATIONAL TRANSACTIONAL ACCESS OF IN-MEMORY DATA GRIDS IN A CLIENT-SERVER ENVIRONMENTAANM Markus; MirceaAACI LondonAACO GBAAGP Markus; Mircea London GBAANM Surtani; ManikAACI LondonAACO GBAAGP Surtani; Manik London GB - A client computing system identifies a start of a multi-operational transaction pertaining to access of data stored in caches being managed by nodes residing in Java Virtual Machines in an in-memory data grid. The client computing system stores transaction context data indicating the start of the multi-operational transaction and identifies an application request to perform an operation pertaining to the multi-operational transaction. The application request is from an application that resides outside of the Java Virtual Machines of the nodes. The client computing system determines the transaction context of the operation based on the transaction context data and sends an operation request over a network to a managing node in the in-memory data grid to manage the multi-operational transaction. The operation request includes header data based on the transaction context data. | 01-17-2013 |
20130151889 | DISK-FREE RECOVERY OF XA TRANSACTIONS FOR IN-MEMORY DATA GRIDS - A data grid node that is hosted by a computing system receives a request to prepare transaction operations for a multi-operational transaction for a commit. The transaction operations are associated with other data grid nodes in the data grid. The data grid node stores transaction state data for the multi-operational transaction in local memory associated with the data grid node and identifies other data grid nodes in the data grid that manage the data pertaining to the transaction operations for the multi-operational transaction. The data grid node sends the transaction state data to the other data grid nodes and the other data grid nodes store the transaction state data in local memory associated with the corresponding data grid node. | 06-13-2013 |
20130226890 | SUPPORTING TRANSACTIONS IN DISTRIBUTED ENVIRONMENTS USING A LOCAL COPY OF REMOTE TRANSACTION DATA AND OPTIMISTIC LOCKING - A first process executing in a computer system in a data grid receives a request to perform at least one transaction operation of a transaction based on remote transaction data of at least one other process in the data grid. The at least one other process is capable to perform a prepare operation for a transaction. The first process identifies a local copy of the remote transaction data in a local data structure and performs the at least one transaction operation using the local copy of the remote transaction data without acquiring a lock on the remote transaction data. | 08-29-2013 |
20130226891 | MANAGING VERSIONS OF TRANSACTION DATA USED FOR MULTIPLE TRANSACTIONS IN DISTRIBUTED ENVIRONMENTS - A first process in a data grid provides an initial version that corresponds to transaction data controlled by the first to a second process and a third process. The first process receives a request of the second process and changes the transaction data based on a first transaction. The first process provides a current version value of the transaction data to the second process and commit the change to the transaction data based on the first transaction if the current version value matches the initial version value provided to the second process and creates a new version value for the transaction data upon committing the change. The first process changes the transaction data based on the second transaction and rolls back the change made to the transaction data based on the second transaction if the new version value does not match the initial version value provided to the third process. | 08-29-2013 |
20130297580 | LOCK REORDERING FOR OPTIMISTIC LOCKING OF DATA ON A SINGLE NODE TO AVOID TRANSACTION DEADLOCK - A node a data grid receives a prepare request identifying data to lock for a first transaction. The prepare request indicates a locking order that is different from a locking order indicated by a prior prepare request of a second transaction using the same data. The node identifies keys that correspond to the data. The keys are co-located on the node. The node ranks the keys to define an order for acquiring locks for the data based on key identifiers that correspond to the keys. The defined order matches a locking order used by the second transaction. The node acquires locks for the data using the defined order. | 11-07-2013 |
20130318314 | MANAGING COPIES OF DATA ON MULTIPLE NODES USING A DATA CONTROLLER NODE TO AVOID TRANSACTION DEADLOCK - A data controller node receives a request to update data stored at the data controller node for a transaction managed by a transaction originator node. The data controller node locks the data at the data controller node and identifies copies of the data residing at other nodes. The data controller node sends a message to the other nodes to update the copy at the other nodes without locking the copy of the data at the other nodes. The data controller node determines whether an acknowledgment is received from each of the other nodes that the copy of the data are updated for the transaction and updates the locked data at the data controller node for the transaction in response to receiving the acknowledgment from each of the other nodes. | 11-28-2013 |
20130325827 | INCREMENTAL OPTIMISTIC LOCKING OF DATA DISTRIBUTED ON MULTIPLE NODES TO AVOID TRANSACTION DEADLOCK - A transaction originator node identifies multiple data elements distributed at multiple enlisted nodes to lock for a transaction managed by the transaction originator node. The transaction originator node determines which of the enlisted nodes is a first enlisted node in a lock order for the transaction and sends an update request to the first enlisted node in the lock order to lock a data element residing at the first enlisted node. The transaction originator node sends update requests to remaining enlisted nodes in the lock order to cache the update requests until the remaining enlisted nodes receive a message to perform a lock. | 12-05-2013 |
20160100006 | Transferring Data Between Sites - The method including, receiving a transfer command at a transfer coordinator node of a first node cluster at a first site to initiate a transfer of data from the first node cluster to a second node cluster at a second site. The method further including causing a status of the second site to be switched from an inactive status to an active status at the nodes of the first node cluster. The method further including initiating a transfer of the data from the first node cluster to the second node cluster. The method further including determining that the second node cluster has the active status at the nodes of the first node cluster and causing the data transaction request to be transferred from the nodes at the first node cluster to the second node cluster during the transfer of the data. | 04-07-2016 |