Asynchronous updates of weakly consistent distributed state information

• US 20040024807A1
• Filed: 07/31/2002
• Published: 02/05/2004
• Est. Priority Date: 07/31/2002
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Cabrera, Luis Felipe, Wortendyke, David A.
• Application Number:
  US10/210,517
• Publication Number:
  US 20040024807A1
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups

Abstract

Information is disseminated, with weak consistency, across multiple computer systems. Update operations may be described in terms of a directed acyclic graph of update dependencies. Using techniques similar to operations logging, state information is recorded and preserved through information units at a particular update operation'"'"'s primary site. Subsequent processing of these information units at the primary site then initiates dissemination of the state information to zero or more dependent sites. Accordingly, an update operation may happen first at its primary site. Then, in a delayed manner, the state information may be updated in the dependent sites thereby eventually synchronizing the over-all state of the system. Upon cessation of update operations of this type, the system will eventually reach a self-consistent stable state.

Claims

1. A method, performed by a primary computer system, of asynchronously performing an update operation on weak-consistent distributed state information, the method comprising:

durably storing an update-operation description that specifies at least one update dependency associated with the update operation;

durably storing primary data to be used for performing a step of the update operation on the primary computer system and dependent data to be used for performing a step of the update operation on at least one dependent computer system;

durably storing an information unit indicating an intention to send the dependent data to the at least one dependent computer system in accordance with the update-operation description;

sending the dependent data to the at least one dependent computer system in accordance with the update-operation description; and

upon receiving, from the at least one dependent computer system, an indication of acceptance of the dependent data, durably storing an information unit indicating that the at least one dependent computer system accepted the dependent data.

2. The method of claim 1, wherein the update-operation description specifies at least one primary operation to be performed by the primary computer system.

3. The method of claim 1, wherein the update-operation description is specified in terms of a directed acyclic graph of update dependencies.

4. The method of claim 1, further comprising:

durably storing an indication of an order in which a plurality of update operations are to be performed.

5. The method of claim 4, further comprising:

durably storing an indication of a last-performed update operation from the plurality of update operations to be performed.

6. The method of claim 5, further comprising:

using the stored indication of a last-performed update operation and the stored indication of an order in which update operations are to be performed to determine whether or not a particular update operation has been performed.

7. The method of claim 4, further comprising:

using sequence numbers to uniquely identify instances of update operations.

8. The method of claim 1, further comprising:

durably storing information pertaining to a plurality of performed update operations thereby enabling replaying of the update operations in the future.

9. The method of claim 8, further comprising:

replaying a plurality of the performed update operations for which pertinent information was previously stored such that;

fault-recovery update operations and normal update operations are processed in substantially the same way, and

the update operations are replayed by at least one of the primary-computer system and a computer system not involved in originally performing the replayed update operations.

10. The method of claim 1, further comprising:

for a particular update operation, durably storing at the primary computer system substantially all primary data targeted for storage at the primary computer system and substantially all dependent data targeted for storage at the at least one dependent computer system.

11. The method of claim 1, further comprising:

durably storing a plurality of serialized information units specifying that the primary computer system will send dependent data associated with a plurality of update operations to a plurality of dependent computer systems.

12. The method of claim 11, further comprising:

sending the dependent data to the plurality of dependent computer systems in accordance with an order in which the serialized information units were stored.

13. The method of claim 12, further comprising:

upon receiving, from the at least one dependent computer system, an indication of completion of dependent operations associated with the dependent data, durably storing at least one information unit indicating completion of the dependent operations.

14. A method, performed by a dependent computer system, of asynchronously performing an update operation on weak-consistent distributed state information, the method comprising:

receiving, from a primary computer system, dependent data that is associated with the update operation;

durably storing the dependent data and then providing an indication to the primary computer system that the dependent computer system has accepted the dependent data;

durably storing an information unit specifying that the secondary computer system will perform local processing associated with the dependent data;

performing the local processing associated with the dependent data; and

durably storing an information unit indicating that the dependent computer system performed the local processing associated with the dependent data.

15. The method of claim 14, further comprising:

storing an indication of an order in which a plurality of dependent operations, which are associated with the dependent data, are to be performed.

16. The method of claim 15, further comprising:

storing an indication of a last-performed dependent operation from the plurality of dependent operations to be performed.

17. The method of claim 16, further comprising:

using the stored indication of a last-performed dependent operation and the stored indication of an order in which the dependent operations are to be performed to determine whether or not a particular dependent operation has been performed.

18. The method of claim 14, further comprising:

storing information pertaining to a plurality of performed dependent operations thereby enabling replaying of the dependent operations in the future.

19. The method of claim 18, further comprising:

replaying a plurality of the performed dependent operations for which pertinent information was previously stored.

20. The method of claim 14, wherein, upon failure of the at least one dependent operation to be performed by the dependent computer system, notifying the primary computer system that the at least one dependent operation to be performed by the dependent computer system has failed.

21. The method of claim 20, wherein:

before notifying the primary computer system that the at least one dependent operation to be performed by the dependent computer system has failed, storing an intention record indicating an intention to notify the primary computer of the failure; and

after notifying the primary computer system that the at least one dependent operation to be performed by the dependent computer system has failed, storing a log record indicating that the primary computer system was notified of the failure.

22. The method of claim 14, further comprising

storing an intention-log record specifying that the secondary computer system will send dependent data stored at the secondary computer system to at least one additional dependent computer system;

sending the dependent data stored at the secondary computer system to the at least one additional dependent computer system; and

upon receiving, from the at least one additional dependent computer system, an indication of acceptance of the dependent data stored at the secondary computer, storing a log record indicating that the at least one additional dependent computer system accepted the dependent data stored at the secondary computer system.

23. A system that asynchronously processes update operations associated with weak-consistent distributed state information, the system comprising:

a primary information-storage site that stores

a plurality of directed acyclic graphs of update dependencies associated respectively with the update operations,

serialized intention-log records of update operations to be performed, and

log records indicating update operations that have been performed; and

at least one dependent information-storage site that;

checks for continuity of counter-sequence values in update information received from the primary information-storage site to detect gaps in, and repeats of, the update information received from the primary information-storage site,

upon detecting a gap in the update information, informs the primary information-storage site that the gap was detected, and

upon detecting a repeat of received update information, ignores the repeated update information.

24. The system of claim 23, wherein, for at least one update operation, the primary information-storage site stores substantially all update information to be used by the primary information-storage site and by the at least one dependent information-storage site.

25. The system of claim 23, wherein dependent site-update information, which is stored at the primary information-storage site, is divided into logical units targeted to various dependent information-storage sites.

26. The system of claim 23, wherein, before sending update information from the primary information-storage site to a dependent information-storage site, the primary information-storage site determines whether any update information negates any other update information to be sent to the dependent information-storage site, and, upon detecting such a negation, removing the negated information from the update information to be sent to the dependent information-storage site.

27. The system of claim 26, wherein:

before removing the negated information from the update information to be sent to the dependent information-storage site, the primary information-storage site stores an intention record indicating an intention to remove the negated information; and

after removing the negated information from the update information to be sent to the dependent information-storage site, the primary information-storage site stores a log record indicating that the negated information was removed from the update information to be sent to the dependent information-storage site.

28. The system of claim 23, wherein, upon detecting an out-of-synchronization condition, the primary information-storage site and at least one of the dependent information-storage sites synchronize their respective state information.

29. The system of claim 28, wherein, the primary information-storage site sends state information to at least one of the dependent information-storage sites in response to receiving a synchronization request from the at least one of the dependent information-storage sites.

30. The system of claim 28, wherein, the primary information-storage site sends state information to at least one of the dependent information-storage sites in response to the at least one of the dependent information-storage sites starting up, recovering from a failure, or re-establishing a connection with the primary information-storage site.

31. The system of claim 28, wherein, when the primary site is behind in time relative to at least one of the dependent sites, then compensatory actions are taken to roll back in time state information stored by the at least one dependent information-storage site.