Communication for version management in a distributed information service

• US 4,714,992 A
• Filed: 11/26/1985
• Issued: 12/22/1987
• Est. Priority Date: 11/26/1985
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Mattson, Richard L., Gladney, Henry M., Lorch, Douglas J.
• Primary Examiner(s): Zache, Raulfe B.
• Application Number:
  US06/801,897
• Time in Patent Office: 756 Days
• Field of Search: 364/200 MS File, 364/300
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2216/09 Obsolescence
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99957 Garbage collection

Abstract

In a distributed processing system network in which at least one node operates as a source location having access to data objects of a database, and at least one other node operates as a replica location storing replicas of data objects from the source location, managing obsolescence of the replicas is performed by having the replica locations submitting requests to the source location for ascertaining obsolescence of data objects. The source location, responsive to a request from a requesting replica location, extracts identifiers of a set of obsolete objects and communicates them to the requesting replica location. Upon receiving the identifiers, the requesting location renders inaccessible those data objects corresponding to the identifiers received. The source location then removes those identifiers that have been communicated to the requesting replica location.

Claims

1. A method for managing obsolescence of replicas of data objects, the objects being utilized in multiple nodes of a distributed processing system in which at least one node operates as an object source location having access to a source database containing source data objects and at least one other node operates as an object replica location having means for storing replicas of requested objects received from a source location, each source data object being alterable whereby replicas of altered objects stored at replica locations may become obsolete, comprising the steps of:

responsive to a request from a first replica location to ascertain obsolescence of data objects, extracting at the source location identifiers of a set of obsolete objects;

communicating said identifiers, if any, as an atomic demand/response transaction to said first replica location;

rendering inaccessible at said first replica location any replicas corresponding to those identifiers received from the source location; and

removing from the source location those identifiers communicated to said first replica location.

2. The method of claim 1, further including the steps of:

associating at the source location a currency version number with said first replica location identifying a set of obsolete versions of source data objects for which identifiers have not been successfully communicated thereto;

associating a data version number with data objects retrieved from the source database to identify a particular version of the data objects retrieved; and

responsive to a request from said first replica location for a target source data object, returning a version of said target source data object being requested, said version having a data version number that is consistent with the currency version number, unless this condition cannot be satisfied.

3. A method for locating and rendering inaccessible obsolete versions of data objects, the objects being utilized in multiple nodes of a distributed processing system in which at least one node operates as an object source location having access to a source database containing source data objects and at least one other node operates as an object replica location having means for storing versions of requested objects received from a source location, each source data object being alterable whereby a plurality of versions are created and versions stored at replica locations may become obsolete, the relative obsolescence of each version at any time t being identifiable by a version number corresponding to its position in a temporal sequence, including an oldest version and a most recent version, among versions of source data objects comprising the steps at each source location of:

maintaining a list of replica locations;

maintaining a list of identifiers of obsolete versions of source data objects for each identified replica location;

responsive to a request at a time t₁ from a first replica location to ascertain obsolescence of at least one data object, extracting from list of identifiers a first subset of identifiers corresponding to versions which have previously been sent to said first replica location, and extracting from the first subset of identifiers, a second subset of identifiers corresponding to versions which are oldest in said temporal sequence at time t₁ ;

sending the second subset of identifiers to said first replica location as one or more messages in an atomic demand/response sequence, any interruption in the sequence resulting in an abort; and

responsive to an acknowledgment from the replica location, deleting the second subset of identifiers from the list of identifiers; and

comprising the steps at said first replica location of;

sending at least once to each source location employed by this replica location, a signal identifying this replica location;

initiating a request to ascertain obsolescence of at least one data object from the source location; and

upon receiving one or more messages from the source location, rendering inaccessible those versions of data objects identified by any one of the messages so received.

4. The method of claim 3, wherein said acknowledgement from the replica location comprises a further request to ascertain obsolescence.

5. The method of claim 3, further including the steps at the source location of:

responsive to a request from a second replica location for a first data object, extracting at a time t_e from said second replica location'"'"'s list of identifiers, the version number of a first identifier corresponding to the oldest version V_oc at t_e whose obsolescence has not yet been successfully communicated to said second replica location; and

sending a version of said first data object having a version number immediately preceding the version number of V_oc if V_oc is older than the version number indicating t_e ;

sending a version of said first data object having a version number immediately preceding the version number indicating t_e if V_oc is newer than the version number indicating t_e ; and

further including the step at the replica location of;

initiating a request for a data object.

6. In a distributed processing system having a network of nodes connected by communication links in which at least one node of the system operates as a source location having access to a source database containing source data objects and at least one other node operates as a replica location having a means for storing replicas of source data objects received from a source location, an apparatus for managing obsolescence of replicas comprising:

manager means, in communication with a source location, for maintaining obsolescence data identifying obsolete replicas;

means at a requesting replica location for generating an invalidation request for at least a portion of the obsolescence data; and

server means, in communication with the manager means and the requesting replica location and responsive to the invalidation request, for supplying the portion of the obsolescence data to the requesting replica location.

7. The apparatus of claim 6, wherein said server means further includes:

interceptor means, connected to a communication link connecting the source location and the requesting replica location, for detecting the invalidation request.

8. The apparatus of claim 6, wherein said manager means supplies the obsolescence data to the requesting replica location as an atomic demand/response transaction.

9. The apparatus of claim 6, further including:

means at the requesting replica location for generating a request for a first replica of a source data object; and

wherein

the obsolescence data includes currency data identifying obsolete versions of data objects that have not been successfully communicated to the requesting replica location; and

the server means includes means responsive to said request for said first replica and the currency data for providing said first replica of source data objects when source data objects consistent with the currency data for the requesting replica location are available, otherwise preventing access to said first replica.

10. The apparatus of claim 9, further including:

buffer means, in communication with the server means, for storing source data objects keyed by requests identifying the source data object and versions of the source data object.