Optimization for transaction failover in a multi-node system environment where objects' mastership is based on access patterns
First Claim
Patent Images
1. A method for transaction failover in a multi-node system, the method comprising:
- causing one or more nodes to execute one or more transactions, said one or more transactions including a certain transaction having been executed on a node that terminated prior to completing said certain transaction;
tracking an affinity relationship between affinity objects and said certain transaction;
transferring said certain transaction to another node;
establishing said another node as master of said affinity objects; and
remastering said affinity objects by transferring affinity relationships to said another node.
1 Assignment
0 Petitions
Accused Products
Abstract
Techniques are provided for responding to the termination of a node executing one or more transactions by selecting another node to complete the transactions, and assigning to the selected node the affinity relationships that existed between the terminated node and the objects being accessed by said transactions.
-
Citations
32 Claims
-
1. A method for transaction failover in a multi-node system, the method comprising:
-
causing one or more nodes to execute one or more transactions, said one or more transactions including a certain transaction having been executed on a node that terminated prior to completing said certain transaction; tracking an affinity relationship between affinity objects and said certain transaction;
transferring said certain transaction to another node;establishing said another node as master of said affinity objects; and remastering said affinity objects by transferring affinity relationships to said another node. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. A method for transaction failover in a multi-node system, the method comprising:
-
causing one or more nodes to execute one or more transactions, said one or more transactions including a certain transaction having been executed on a node that terminated prior to completing said certain transaction; associating affinity objects with said certain transaction; creating an affinity relationship between said terminated node and said affinity objects; and transferring said affinity relationship for said affinity objects of said certain transaction to a failover node; wherein said transferring causes remastering. - View Dependent Claims (26, 27, 28, 29, 30, 31, 32)
-
Specification