MANAGING COPIES OF DATA ON MULTIPLE NODES USING A DATA CONTROLLER NODE TO AVOID TRANSACTION DEADLOCK

• US 20130318314A1
• Filed: 05/25/2012
• Published: 11/28/2013
• Est. Priority Date: 05/25/2012
• Status: Abandoned Application

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Markus, Mircea, Surtani, Manik
• Application Number:
  US13/481,635
• Publication Number:
  US 20130318314A1
• Time in Patent Office: Days
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 12/16 Protection against loss of memory contents contains no material, see G06F11/00
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details

Abstract

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.

Claims

1. A method comprising:

receiving, by a data controller node in a data grid, an update request to update data stored at the data controller node for a transaction managed by a transaction originator node;

locking the data for the transaction at the data controller node;

identifying a copy of the data residing at one or more other nodes in the data grid;

sending a message to the one or more other nodes to update the copy of the data at the one or more other nodes for the transaction without locking the copy of the data at the one or more other nodes;

determining whether an acknowledgment is received from each of the one or more other nodes that the copy of the data at the one or more other nodes are updated for the transaction; and

updating the locked data at the data controller node for the transaction in response to receiving the acknowledgment from each of the one or more other nodes.

2. The method of claim 1, further comprising:

releasing the lock on the data at the data controller node.

3. The method of claim 1, further comprising:

sending a message to each of the one or more other nodes to rollback data at the one or more other nodes to a previous state in response to not receiving the acknowledgment from each of the one or more other nodes; and

releasing the lock on the data at the data controller node.

4. The method of claim 1, further comprising:

locking the data at the data controller node for a second transaction managed by a second transaction originator node; and

sending a message to the one or more other nodes to update the copy of the data at the one or more other nodes for the second transaction without locking the copy of the data at the one or more other nodes.

5. The method of claim 1, further comprising:

sending a message to transaction originator node indicating whether the data stored at the data controller node is updated for the transaction.

6. A method comprising:

identifying, by a first transaction originator node in a data grid, data to lock for a first transaction managed by the first transaction originator node, wherein the data matches data for a second transaction managed by a second transaction originator node;

determining by the first transaction originator node, that copies of the data resides at a plurality of enlisted nodes;

determining, by the first transaction originator node, which of the plurality of enlisted nodes is a data controller node for the data for the first transaction, wherein the data controller node for the first transaction matches a data controller node for the second transaction; and

sending, by the first transaction originator node, an update request for the first transaction to the data controller node, wherein the data controller node acquires a lock on the data for the first transaction and sends a message to remaining enlisted nodes in the plurality of enlisted nodes to update a copy of the data at the corresponding enlisted node without acquiring a lock on the copy of the data at the corresponding enlisted node.

7. The method of claim 6, wherein determining which of the plurality of enlisted nodes is a data controller node comprises:

determining a hash value for each of the plurality of enlisted nodes using corresponding node identifiers; and

ranking the plurality of enlisted nodes based on the hash values.

8. The method of claim 7, wherein the data controller node is the enlisted node having one of a greatest hash value or a least hash value.

9. The method of claim 6, wherein determining which of the plurality of enlisted nodes is a data controller node comprises:

accessing a list of a plurality of nodes in the data grid; and

identifying the data controller node based on positions in the list of the enlisted nodes that correspond to the data for the first transaction.

10. A non-transitory computer-readable storage medium including instructions that, when executed by a processing device at a data controller node in a data grid, cause the processing device to perform a set of operations comprising:

receiving, by the data controller node, an update request to update data stored at the data controller node for a transaction managed by a transaction originator node;

locking the data for the transaction at the data controller node;

identifying a copy of the data residing at one or more other nodes in the data grid;

sending a message to the one or more other nodes to update the copy of the data at the one or more other nodes for the transaction without locking the copy of the data at the one or more other nodes;

determining whether an acknowledgment is received from each of the one or more other nodes that the copy of the data at the one or more other nodes are updated for the transaction; and

updating the locked data at the data controller node for the transaction in response to receiving the acknowledgment from each of the one or more other nodes.

11. The non-transitory computer-readable storage medium of claim 10, the operations further comprising:

releasing the lock on the data at the data controller node.

12. The non-transitory computer-readable storage medium of claim 10, the method further comprising:

sending a message to each of the one or more other nodes to rollback data at the one or more other nodes to a previous state in response to not receiving the acknowledgment from each of the one or more other nodes; and

releasing the lock on the data at the data controller node.

13. The non-transitory computer-readable storage medium of claim 10, the operations further comprising:

locking the data at the data controller node for a second transaction managed by a second transaction originator node; and

sending a message to the one or more other nodes to update the copy of the data at the one or more other nodes for the second transaction without locking the copy of the data at the one or more other nodes.

14. The non-transitory computer-readable storage medium of claim 10, the operations further comprising:

sending a message to transaction originator node indicating whether the data stored at the data controller node is updated for the transaction.

15. A system comprising:

a memory; and

a processing device in a data grid, the processing device coupled to the memory and configured to execute a process to

receive an update request to update data stored at the data controller node for a transaction managed by a transaction originator node,

lock the data for the transaction at the data controller node,

identify a copy of the data residing at one or more other nodes in the data grid,

send a message to the one or more other nodes to update the copy of the data at the one or more other nodes for the transaction without locking the copy of the data at the one or more other nodes,

determine whether an acknowledgment is received from each of the one or more other nodes that the copy of the data at the one or more other nodes are updated for the transaction, and

update the locked data at the data controller node for the transaction in response to receiving the acknowledgment from each of the one or more other nodes.

16. The system of claim 15, wherein the processing device is further configured to:

release the lock on the data at the data controller node.

17. The system of claim 15, wherein the processing device is further configured to:

send a message to each of the one or more other nodes to rollback data at the one or more other nodes to a previous state in response to not receiving the acknowledgment from each of the one or more other nodes; and

release the lock on the data at the data controller node.

18. The system of claim 15, wherein the processing device is further configured to:

lock the data at the data controller node for a second transaction managed by a second transaction originator node; and

send a message to the one or more other nodes to update the copy of the data at the one or more other nodes for the second transaction without locking the copy of the data at the one or more other nodes.

19. The system of claim 15, wherein the processing device is further configured to:

send a message to transaction originator node indicating whether the data stored at the data controller node is updated for the transaction.