MANAGING MULTI-NODE MULTI-VERSION SYSTEMS
First Claim
1. A computer implemented method for managing a multi-node multi-version system, the computer implemented method comprising:
- associating a version identifier with a first version of data available at a first node in the multi-node multi-version system, the version identifier corresponding to the first version of the data, the data including an update;
sending the data and the associated version identifier to a second node without learning a second version of data available at the second node, wherein one of (i) the first version of data is a subset of the second version of data, and (ii) the second version of data is a subset of the first version of data; and
repeating the sending for each update at the first node.
1 Assignment
0 Petitions
Accused Products
Abstract
A method, system, and computer usable program product for managing multi-node multi-version systems are provided in the illustrative embodiments. A process associates a version identifier with a first version of data available at a first node in the multi-node multi-version system. The version identifier corresponds to the first version of the data. The data includes an update. The process sends the data and the associated version identifier to a second node without learning a second version of data available at the second node. In one embodiment, the first version of data may be a subset of the second version of data. In another embodiment the second version of data may be a subset of the first version of data. The process repeats the sending for each update at the first node.
12 Citations
20 Claims
-
1. A computer implemented method for managing a multi-node multi-version system, the computer implemented method comprising:
-
associating a version identifier with a first version of data available at a first node in the multi-node multi-version system, the version identifier corresponding to the first version of the data, the data including an update; sending the data and the associated version identifier to a second node without learning a second version of data available at the second node, wherein one of (i) the first version of data is a subset of the second version of data, and (ii) the second version of data is a subset of the first version of data; and repeating the sending for each update at the first node. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer usable program product comprising a computer usable medium including computer usable code for managing a multi-node multi-version system, the computer usable code comprising:
-
computer usable code for associating a version identifier with a first version of data available at a first node in the multi-node multi-version system, the version identifier corresponding to the first version of the data, the data including an update; computer usable code for sending the data and the associated version identifier to a second node without learning a second version of data available at the second node, wherein one of (i) the first version of data is a subset of the second version of data, and (ii) the second version of data is a subset of the first version of data; and computer usable code for repeating the sending for each update at the first node. - View Dependent Claims (11, 12, 13, 14, 15)
-
-
16. A data processing system for managing a multi-node multi-version system, the data processing system comprising:
-
a storage device, wherein the storage device stores computer usable program code; and a processor, wherein the processor executes the computer usable program code, and wherein the computer usable program code comprises; computer usable code for associating a version identifier with a first version of data available at a first node in the multi-node multi-version system, the version identifier corresponding to the first version of the data, the data including an update; computer usable code for sending the data and the associated version identifier to a second node without learning a second version of data available at the second node, wherein one of (i) the first version of data is a subset of the second version of data, and (ii) the second version of data is a subset of the first version of data; and computer usable code for repeating the sending for each update at the first node. - View Dependent Claims (17, 18, 19, 20)
-
Specification